Automations

Set up rules to automatically move, update, and act on tasks so you can focus on the work that matters.

By Byte Size Labs · Updated 21 April 2026

Automations are available on the Teams plan. Upgrade in Settings › Billing to unlock this feature.

What Are Automations?

Automations are “if this, then that” rules that trigger actions whenever a specified condition is met. Instead of manually updating tasks or sending reminders, you configure a rule once and Chronos handles the rest.

Example automations:

When a task is marked complete → send a notification to a team member
When a task's due date passes → automatically move it to an “Overdue” project
When a new task is added to a project → assign it to a specific person
When a task reaches High priority → add it to your Daily Brief

Creating an Automation

Step-by-step

Go to Settings › Automations
All your automations are managed from a single place in Settings.
Click "New Automation"
Opens the rule builder where you define the trigger and action.
Choose a trigger
Select the event that starts the automation — see triggers below.
Choose an action
Select what happens when the trigger fires — see actions below.
Name and save
Give the automation a descriptive name and toggle it on.

Available Triggers & Actions

Triggers (When…)

Task is created
Task is completed
Task due date passes
Task priority changes
Task is added to a project
Task is assigned to a team member

Actions (Then…)

Send a notification
Assign to a team member
Move task to a project
Set task priority
Add a label or tag
Trigger a webhook

Managing Automations

Toggle on/off: Pause and resume automations without deleting them — useful for seasonal workflows
Run history: See when each automation last fired and whether it succeeded
Edit: Modify triggers and actions at any time; changes apply to future runs only
Delete: Removes the automation permanently; tasks already affected are not reverted

Tips for effective automations:

Start with one automation and observe its behaviour before adding more — complex rule chains can be hard to debug
Use descriptive names like “Overdue → move to Backlog” so you can identify rules at a glance
Automations run in the order listed — if two rules conflict, the last one wins
Check the run history if an automation isn't firing as expected — it shows any errors

Need more help? Contact support or return to help centre