Automations
Automations are event-driven rules that execute actions when specific triggers fire. Define "when X happens, do Y" rules to eliminate repetitive work.
Triggers
These events can start an automation:
| Trigger | Fires When |
|---|---|
| Task Created | A new task is added |
| Task Completed | A task is marked done |
| Task Updated | Any task field changes |
| Meeting Created | A new meeting is scheduled |
| Meeting Ended | A video call finishes |
| Document Updated | A document is saved |
| Email Received | An email arrives in your inbox |
| Calendar Event Created | A new calendar event is added |
| Timer Started | A focus timer begins |
| Timer Stopped | A focus timer ends |
Actions
When a trigger fires, one of these actions runs:
| Action | What It Does |
|---|---|
| Send Notification | Push a notification to the user |
| Create Task | Automatically create a new task |
| Create Document | Generate a new document |
| Send Email | Send an email |
| Log Event | Record the event to the automation log |
Creating an Automation
- Navigate to Automations in the sidebar
- Click New Rule
- Enter a name (e.g., "Meeting follow-up")
- Select a When trigger from the dropdown
- Select a Then action from the dropdown
- Optionally add a Condition as JSON to filter events (e.g.,
{"priority":"high"}to only fire for high-priority tasks) - Click Create
Templates
Eight pre-built templates are available for common workflows:
- Meeting follow-up — meeting.ended → create_task
- Task completion alert — task.completed → notify
- Email to task — email.received → create_task
- Meeting notes — meeting.ended → create_doc
- New task notification — task.created → notify
- Document change log — document.updated → log
- Calendar reminder email — calendar.created → send_email
- Focus session log — timer.stopped → log
Click any template to pre-fill the automation form, then customize the name and conditions.
Managing Automations
Each automation card shows:
- Enable/disable toggle — turn rules on or off without deleting them
- Trigger → Action — visual chips showing the event flow
- Run count — how many times this rule has fired
- Last ran — relative timestamp of the most recent execution
- Edit/Delete buttons
Dashboard Stats
At the top of the automations page:
- Active — number of enabled rules
- Total Rules — all rules including disabled ones
- Total Runs — cumulative execution count across all rules
Automation Logs
Click Logs to view the execution history. Each log entry shows the trigger event, the action taken, and when it ran.
Conditions
The optional condition field accepts a JSON object that is matched against the event payload. Only events matching all specified fields will trigger the action. Leave empty to fire on every matching event.