​
Definition

An Automation is a repeatable agent-work definition. It combines instructions, an Agent owner, optional goal or project context, a trigger, an output route, priority, and a concurrency policy. Triggers can be scheduled, manual or API-driven, or webhook-based. Each dispatch creates an Automation run record, even when concurrency or eligibility causes the dispatch to skip or coalesce. The record connects the trigger to the Issue, Chat, and Agent Run that handled the work. Output has two modes. A tracked Issue enters the normal Issue lifecycle. Chat output creates a separate Messenger conversation for each real execution. See Automation output routing for the authoritative comparison.

​
One illustrative case

An operations owner wants a digest every weekday evening. The Automation names a reporting Agent, links the operations project, and asks for completed work, blockers, and the next decision. Each execution sends its result to a new Chat, where the owner can inspect that run without mixing it with yesterday’s digest.

​
When it is useful

Use an Automation after the trigger, owner, instructions, and result destination are predictable. Keep exploratory work in Chat or an Issue while the request is still changing. Built-in templates are editable starting values in the creation form; selecting one does not create an Automation until the operator submits it. The current lifecycle has active and paused states. Pause an Automation when its definition and history should remain visible but new dispatches should stop. Return it to active when the definition is ready to run again.

​
Operating boundaries

Automations belong to one organization. Linked goals, projects, parent Issues, and assignees must remain in that organization. A schedule is evaluated with its stored timezone. The current UI uses the browser’s local timezone when it creates or edits that schedule. External triggers require replay and idempotency protection. The highest-risk boundary is duplicate work. Concurrency policy decides whether active work causes a new dispatch to enqueue, skip, or coalesce. A skipped or coalesced run must still explain why no new Chat or Issue appeared, and it must not create an empty conversation. Follow Create an Automation to build and verify one.