Sign up →
Help Center › Workflow
Workflow

Automation recipes library

Practical rule patterns for assignment, approval, reminders, escalation, and completion.

These are patterns worth copying. Each one solves a specific repeated problem, and each is narrow enough to explain in a sentence, which is the test of a rule worth keeping.

Assignment on entry

When a task enters a stage, assign it to the person or team who owns that stage. This is the highest-value first rule for most teams because it removes the daily question of whose turn it is.

Request approval at client review

When work reaches your Client Review stage, request approval from the named client approver automatically. This removes the delay caused by somebody forgetting to ask, which is a surprisingly large share of total cycle time.

Overdue escalation

When a due date passes and the task is not complete, notify the owner and, if it stays overdue, the manager. Escalate on a delay that matters rather than on every missed date, or the notification stops meaning anything.

Reminder before a deadline

Notify the owner a set period before a due date rather than after it. Prevention is cheaper than escalation, and this is the rule that most reduces the number of overdue tasks in the first place.

Completion tidy-up

When a task is approved, move it to the finished stage and notify whoever was waiting. Ending work cleanly is what keeps the board readable, and a readable board is what keeps people using it.

What success looks like

  • A handful of narrow, clearly named rules handle the repetitive steps, each is visible in the run ledger, and nobody is doing assignment or chasing by hand.

Common mistakes to avoid

  • Building one rule that tries to handle several situations.
  • Notifying on every stage change, which trains people to ignore notifications.
  • Leaving obsolete rules enabled so the board changes for unexplained reasons.
Questions

Common questions

Free includes none, Studio five per workspace, Agency twenty-five, and Scale is unlimited.

Yes. Use the dry run to see what a rule would have done without it acting.

Need help applying this workflow?

Tell us how your team works and we will help you set this up on a real project.