Automations

Automation rules that you define for your workspace. Every audit event (task.created, task.completed, comment.created, and so on) is matched against your active rules, and matching rules run actions such as set field, apply label, notify user, call webhook, or set an engagement status. The builder is dropdown-driven end to end, with no typing of field names or event strings.

• Template gallery: ready-made workflows in the categories intake, hygiene, notifications and workflow, with zero typing to instantiate
• Trigger dropdown: common audit patterns (task.created, task.status_changed, project.*, comment.*) with human-readable labels
• Actions: set a field (task or project, from the allowed list), apply a label, notify a user, call a webhook or set an engagement status, each chosen with a picker
• Per-rule run history with status, duration and the error of each failed step

• A rule whose action causes the event that triggers it can run again and again. Give each rule a trigger that its own actions do not cause. The record of an automation run never starts another run.
• The webhook a rule calls is one of your webhook subscriptions. A failed delivery is retried on a growing schedule, and failures surface in the delivery log under /settings/webhooks.
• set_field is limited to a whitelist (Task: status/priority/title/description/dueOn/startsOn; Project: status/name/ownerId). Other fields are intentionally unreachable from automations.

1. 1Click From template to pick a ready-made workflow (recommended).
2. 2Or click Custom, pick a trigger from the dropdown, then add one or more actions, each configured via dropdowns.
3. 3Toggle the power icon on the list to enable or disable a rule without deleting it.
4. 4Review the run log to confirm the rule fires as expected before you rely on it.

Why can only certain fields be set by set_field?

Only the listed fields can be written by a rule. Anything else is refused, so a rule cannot change a field outside that list. Use the regular API for other fields, so their own validations run.

Can I edit a template?

Create from a template, then edit the resulting rule like any other. The template is a construction aid, not a runtime link.

Why has an automation triggered itself repeatedly?

A rule whose action matches its own trigger will loop. Give each rule a distinct trigger pattern so an action cannot cause the event that started it.