A Before Action runs while the transition dialog is open, before the state change is committed. An After Action runs once the record has already moved to its new state. Most post-transition automation – creating a task, sending a summary email, notifying an external system – belongs in After Actions because the state change is the prerequisite for that logic.
After Actions are often used in combination with Blueprint SLAs. When a record enters a new state, the After Action might create a task with a due date aligned to the SLA timer, ensuring the assignee knows their deadline as soon as the record arrives in their queue.
A Blueprint After Action is an automated action that runs once a Blueprint Transition is confirmed and the record has moved to its new state. It is used for post-transition tasks such as sending notifications, creating follow-up activities, updating related records, or triggering external integrations.
After Actions support the same types as other Workflow Actions: Field Update, Email Notification, Create Task, Webhook, and Custom Function. Multiple After Actions of different types can be combined in a single transition.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.