Automation & API
Build your first automation
A When / If / Then rule, and the two guards that stop rules looping.
- Open Automations and create a rule.
- When — pick the event: a task created, updated or moved, or a comment added. A rule can also run on a schedule instead.
- If — add conditions on the task’s own fields: priority, issue type, column, assignee, title, days since last update, days since created, days until due. Leave it empty to run on every matching event.
- Then — pick the action: move to a column, set a priority, assign someone, add a label, or notify.
Why it cannot loop
An action produces a new event, which could trigger the rule again. Two guards stop that: the same rule will not run twice on the same task within 60 seconds, and every action refuses to rewrite a value that is already correct — so it emits no event at all.
What the run log tells you
Every run is recorded as succeeded, skipped or failed. A rule whose condition did not hold is skipped — it did nothing, and nothing was meant to happen. A rule that ran and failed did nothing either, but it was supposed to: the automation health card counts the work done for you this month and names the five rules that failed most, so a rule that has been throwing all month has somewhere to say so.
Runs are unlimited on every plan. Free gets 3 rules, Pro 1,000 and Business 10,000. Rules can only be created by Admins and above — a rule with no project set covers the whole organization.