Automations let routine steps happen on their own. A rule pairs a trigger (something that happens to a task) with one or more actions (what the project should do in response), and optional conditions that narrow when it applies.
Create an automation
Open the Automations tab
In your project, go to Settings and choose Automations. You need the Admin role in the project to create or edit rules.
Pick a trigger
Choose what starts the rule, for example when a task is moved to another column, or when a task becomes due soon or overdue. Due-date triggers are checked periodically in the background rather than the instant a deadline passes.
Add conditions (optional)
Narrow the rule by priority, assignee, tags, column, title, description, or due date. All conditions must match for the rule to run.
Choose actions and save
Pick what happens: move the task to a column, assign it to someone, add a tag, set its priority, add a comment, send a notification, or create a subtask. A rule can run several actions in order.
Test, enable & monitor
- Test: each rule has a Test option that dry-runs it so you can check the outcome before it affects real tasks.
- Enable or disable: rules have an on/off toggle, so you can pause one without deleting it.
- Usage: each rule shows how many times it has executed and when it last ran.
Examples that work well
- When a task moves to a Review column, assign it to the reviewer and add a comment.
- When a task becomes overdue, set its priority to Urgent and send a notification.
- When a task becomes due soon, add a tag such as due-this-week so filters catch it.