When / If / Then
One triggering event, as many conditions as you like, and an action. All three are built in a visual builder.
Scheduled rules
Some work answers to a clock, not an event. A rule can be triggered by either.
It cannot loop
A rule’s action produces a new event. A cooldown and no-op guards cut that chain.
How it works
Trigger: something that happened on the board
A task created, updated or moved, or a comment added. Rules listen to the product’s internal event bus — the same source that feeds webhooks and Slack alerts.
Condition: a field on the task
A condition looks at one of priority, issue type, column, assignee, title, days since last update, days since created, days until due. If the condition does not hold, the rule is recorded as skipped and stays in your list, ready for the next event.
Action: move, prioritize, label, notify
Every action is no-op guarded: if the task is already in that column or already at that priority, the rule does nothing — so it produces no new event either.
Every run is on the record
You can see when a rule ran, was skipped, or failed. The automation health card puts the work done for you this month next to the five rules that failed most.
The abuse shield is about speed, not volume
The same rule will not run twice on the same task within 60 seconds, and scheduled rules are processed in a bounded batch each tick. These are safety limits that work the same on every plan — not a wall anybody meets halfway through a month.
Which plan is this on?
Unlimited automation runs — on every plan. The free plan gets 3 rules. Pro carries 1,000 and Business 10,000. A rule you set up never goes quiet mid-month: what a paid plan buys is how many different jobs you can teach the engine, not how often it runs them.
Frequently asked questions
Can a rule get stuck in an infinite loop?
Two guards work together. The same rule will not run twice on the same task within 60 seconds, and every action refuses to rewrite a state that is already correct — so it emits no new event. Between them the chain is cut at the source.
Who can build rules?
Admins and above. A rule with no project selected covers the whole organization and its actions run with the project owner’s identity, so the bar is deliberately high.
How many times a month can a rule run?
There is no limit, on any plan. A run is a handful of queries against our own database, and metering it would mean a rule you set up could go quiet halfway through a month. What the free plan limits is how many rules you can have running at once.