Workflow steps can be configured with automated actions that run at key moments in a card's lifecycle. These automations let you send emails, SMS messages, update tags, modify data, and trigger campaigns without manual intervention.
Each step has four trigger points where you can attach automated functions:
| Trigger | When it fires |
|---|---|
| Entry Functions | When a card enters this step |
| Exit Functions | When a card leaves this step |
| Success Functions | When a card completes this step successfully |
| Fail Functions | When a card fails this step (e.g. requirements not met by due date) |
You can add multiple functions to each trigger. They all run when the trigger fires.
Automatically send an email when the trigger fires. The email is sent to the profiles linked to the workflow card. This is useful for notifying people about status changes, reminders, or next steps.
Send an SMS message to the profiles linked to the card. Great for urgent notifications or time-sensitive communications.
Trigger an email campaign to the people associated with the card. This allows you to send more complex, designed email communications as part of your workflow.
Automatically add a tag to the card or related profiles when the trigger fires. Tags are useful for categorisation and filtering.
Remove a specific tag from the card or related profiles. Useful for cleaning up tags from previous steps.
Update field values on the card or related items. This lets you automatically change data as cards move through steps.
Steps also have a Completion Behaviour setting that determines when the system evaluates whether a card's requirements have been met:
When a card completes or fails a step, you can configure what happens next:
The same options are available for failure actions. Common patterns include:
The system includes automatic loop detection. If an automation causes a card to move through a step it has already visited in the same automation chain, the loop is detected and stopped to prevent infinite processing.
Here's how automations might be configured for an employee induction workflow: