Triggers, conditions and actions
The full vocabulary of the automation engine.
Triggers
| Trigger | Fires when |
|---|---|
| A task is created | Any new task, from any source (manual, email, form, recurring) |
| A task status changes | The task moves between board columns |
| A task is assigned | Someone is added to a task |
| A task is due within 24 hours | Hourly check; once per day per task |
| A deal moves to another stage | A CRM deal changes pipeline stage |
| A support ticket is created | New ticket from any channel including email |
| An invoice becomes overdue | Hourly check on unpaid/partial invoices past due date |
| An intake form is submitted | A public form creates its record |
Conditions
Project is / is not; Priority is / is not; Status is / is not; Deal stage is / is not. Stack as many as you need: all must pass.
Actions
| Action | What it does |
|---|---|
| Change task status | Moves the task to a chosen column |
| Assign user | Specific person, round robin, or least loaded (see Auto-assignment) |
| Add a comment | Posts a comment; supports placeholders |
| Create a task | Spawns a follow-up task with a due date offset |
| Send an email | To assignees, the project client, or custom addresses |
| Send in-app notification | Bell notification to assignees or chosen people |
| Move deal to stage | Advances a CRM deal |
| Set priority | low / medium / high |
| Set due date | N days from now |
| Send client a reminder email | Polite nudge to the record's client |
Placeholders
In comment and email text you can use {title}, {project}, {due_date} and {id}; they are replaced with the record's values when the rule fires.