Blog
How teams use board templates
TSK-2702
Automations
Let the board handle the routine moves
Automations are simple rules for one board: when something happens to a task, do up to three things. They cover the steps your team repeats a dozen times a week, and every run is written in the task's activity.
Included on Pro and Business. Pro comes with a 14-day free trial.
One trigger, up to three actions
Easy to read, easy to check, easy to turn off.
Six triggers, ten actions
Moves, labels, completions, checklists, and due dates.
Logged on the task
Every run shows in activity, and failures show on the rule.
No loops
A rule's changes never trigger another rule.
How a rule reads
Each rule is one sentence: when a task moves to In review, assign Jonas and set the due date two days out. Pick the trigger, add up to three actions, name it, and save. Rules run on the server right after the change, so they work the same whether the change came from the app, the REST API, an AI assistant, or a request form.
- **Triggers:** a task moves to a list, a task is created in a list, a label is added, a task is completed, its checklist is finished, or the due date passes.
- **Actions:** assign, unassign, add a label, remove a label, set priority, set the due date a number of days out, move to a list, mark done, post a comment, or notify assignees, followers, the creator, or a named person.
Start from a recipe
The Automations dialog suggests rules that fit the board's own lists and labels. Use one as it is or edit it first.
- **Review handoff:** when a task moves to Review, assign me and set it due in two days.
- **Escalate overdue work:** when the due date passes, set priority to Urgent and notify the assignees.
- **Checklist done → review:** when a checklist is finished, move the task to Review.
- **Bugs are high priority:** when the Bug label is added, set priority to High.
- **Tell the requester it's done:** when a task is completed, notify the person who created it.
Safe by design
Rules are kept simple on purpose. A rule's own changes don't trigger other rules (or itself), so a board can't end up in a loop. If a rule fails, the change that triggered it still saves, the rule's writes are rolled back, and the error shows on the rule. Each rule shows how many times it has run and when it last ran.
Who can set them up
Anyone who can edit a board can create and change its rules. Guests can't. Rules belong to one board, so a design board and a sprint board can follow different habits.
Common questions
Which plans include automations?
Pro and Business. Owners and admins can upgrade in Settings → Plan & billing, and Pro starts with a 14-day free trial. See pricing.
How quickly does a due-date rule run?
Rules triggered by a change run immediately. The “due date passes” trigger is checked every hour, so it runs within an hour of the task becoming overdue.
Can one rule trigger another?
No. Changes made by a rule never trigger other rules. This keeps boards predictable and prevents loops.
Do automations work with tasks created from forms or email?
Yes. A task created by a request form, email-to-task, the REST API, or an AI assistant triggers “created in a list” rules just like one made in the app.
How do I see what a rule did?
Each run is written in the task's activity under the rule's name. The rule itself shows its run count, its last run, and the last error if one failed.
Related
TasksA Taskeni task carries everything the work needs: subtasks, checklists, blockers, custom fields, files, and the conversation. All of it is on every plan, Free included.IntegrationsTaskeni sends updates out and takes work in: Slack, GitHub, email, public request forms, webhooks, a REST API, and a calendar feed. Every integration is on every plan, Free included.ReportsReports show cycle time, throughput, and the overdue trend for one board or the whole workspace, over the last 4, 12, or 26 weeks. They're built from the tasks you already track, so there's nothing extra to fill in.Development teamsBreak features down, mark what's blocked, estimate and track time, and see pull requests on the task they close. Your coding assistant can read and update the same board.