A rule watches for something happening and then does something. That is the whole model, and keeping it that small is what makes the results predictable.
Availability
Automation rules and recurring tasks are included from the Studio plan.
Every rule has three parts:
A rule can be run against your existing data as a simulation. It reports what it would have done, without doing any of it.
This matters more than it sounds. The classic automation failure is a rule that looks right, gets enabled on a Friday, and quietly reassigns four hundred tasks over the weekend. Simulating first turns that into a list you can read.
Every execution is recorded: what triggered it, what it changed and whether each effect succeeded. When somebody asks why a task moved, the answer is in the run history rather than in a guess.
Separate from rules, and simpler: work that comes back on a schedule creates itself. Monthly reporting, weekly backups, the quarterly licence review.
Pair a recurring task with a task template and the checklist arrives already filled in.
Automation is worth it for work that is genuinely mechanical and happens often. It is a poor substitute for a decision.