A Before Action runs while the transition dialog is still open – before the record’s state actually changes. This makes Before Actions suitable for: validating external data (calling an API to check credit limit before approving a deal), pre-populating fields in the transition dialog, or sending a notification that prompts someone to review the transition before it finalises.
A Blueprint After Action runs once the transition has been confirmed and the record has moved to its new state. After Actions are used for post-transition automation – creating tasks, sending confirmation emails, updating related records.
Before Actions support: Field Update, Email Notification, Webhook, and Custom Function.
A Blueprint Before Action is an automated action configured on a Blueprint Transition that runs before the transition is confirmed and the record moves to the next state. It is used for validation, pre-population of fields, or notifications that need to happen as part of the transition process rather than after it.
A Custom Function configured as a Before Action can return a validation error that prevents the transition from completing if certain conditions are not met – effectively acting as a guard that blocks the transition when the data does not pass the check.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.