​
What an Automation does

An Automation saves a repeatable request together with:
  • the Agent responsible for it
  • an optional goal or project
  • what starts it
  • where the result should appear
  • what to do if the previous run is still active
You can start one manually, on a schedule, through an API call, or from a webhook.

​
Example: a weekly operations summary

Every Monday morning, a reporting Agent summarizes completed work, blockers, and decisions needed this week. Each result opens in a new Chat, so the current report does not get mixed with last week’s conversation. If the summary needs assignment, status, dependencies, or a formal reviewer, send each run to an Issue instead.

​
Automate only after the task is stable

First run the request manually in Chat or an Issue. Create an Automation after you know:
  • when it should run
  • which Agent can handle it
  • what context it needs
  • what a useful result looks like
  • who will notice and fix failures
Templates only fill the creation form. You can edit them before saving, and no Automation exists until you submit the form.

​
Avoid duplicate work

If a new trigger arrives while the previous run is active, the concurrency setting can queue, skip, or combine the new request. The Run history explains what happened even when no new Chat or Issue was created. Pause an Automation while fixing its Agent, instructions, schedule, context, or output destination. The current UI uses your browser’s local timezone when you create or edit a schedule. Follow Create an Automation for a complete setup.