Deliver Workspace
Automations
Automations are trigger-based rules that run automatically when task events happen. Available on the Team plan and above.
How automations work
Every automation has three parts: a trigger (what fires the rule), optional conditions (filter which tasks it applies to), and one or more actions (what happens).
WHEN task.status_changed
AND status equals BLOCKED
THEN send_notification "Task blocked — needs attention"
AND status equals BLOCKED
THEN send_notification "Task blocked — needs attention"
Triggers
| Trigger | Fires when |
|---|---|
| task.created | A new task is created in any project |
| task.status_changed | A task's status field changes |
| task.assigned | A task is assigned to a user |
| task.due_date_passed | A task's due date passes without completion (daily cron) |
Conditions
Conditions filter which tasks the automation applies to. You can combine multiple conditions.
| Field | Operators |
|---|---|
| status | equals · not_equals |
| priority | equals · not_equals |
| sectionId | equals · not_equals |
| projectId | equals · not_equals |
| assigneeId | equals · not_equals · contains |
Actions
| Action | What it does |
|---|---|
| set_status | Change the task status to any valid status |
| set_priority | Change the task priority |
| assign_user | Assign the task to a specific user |
| add_label | Add a label to the task |
| send_notification | Push an in-app notification with a custom message |
| move_to_section | Move the task to a different section |
Default automations
When you create your first project, GrowthOS seeds three smart defaults (only once per org, won't overwrite existing rules):
- Notify PM when a task is marked BLOCKED
- Escalate overdue tasks (due_date_passed trigger)
- Set new tasks to MEDIUM priority
AI Automation Builder
Don't want to configure triggers and actions manually? Describe the rule in plain English and GrowthOS generates the full automation config. See AI Features for details.