An Automation is a Space-owned definition for repeatable Agent or Crew work. It combines instructions, an execution assignee, one or more triggers, and run history. Current Automations start Agent or Crew runs directly; they do not create a Task for each run.Use an Automation when the same well-defined work should be started repeatedly or in response to a predictable event.What an Automation contains#
Name and instructions describing the goal, steps, constraints, and expected result.
Space that owns the Automation.
Assignee: an Agent or Crew that performs the work.
Status: Active or Paused.
Triggers that start runs.
Run history with the source, result, Agent run, and failure reason when available.
Write useful instructions#
Automation instructions should state:The inputs or context to inspect.
Where the result should be recorded.
Which changes are allowed.
When a person must review or decide.
Trigger types#
Schedule#
A schedule uses a standard five-field cron expression and a timezone. The UI provides common hourly, daily, weekday, and weekly choices as well as custom cron.Use schedules for recurring checks, summaries, reminders, or maintenance work.Task status#
A task-status trigger starts when a task moves into one selected Organization status.Statuses are reusable across Space task type Workflows. Current event matching is Organization-wide: if the same status is used in several Spaces, a matching transition in any of those Spaces can start the Automation. Choose a status that represents the intended scope, and make the instructions verify the triggering task before making changes.A comment trigger starts when a task comment contains a configured phrase. Matching is case-insensitive and checks whether the phrase occurs anywhere in the comment.Current comment matching also listens across the Organization rather than filtering by the Automation's owning Space. Prefer a distinctive slash command or phrase and validate the triggering task in the instructions.Webhook#
A webhook trigger creates a secret URL that accepts a POST request from an external service. The full URL is shown when the trigger is created or regenerated and is not available for later viewing.By default, the URL acts as a bearer secret. If a signing secret is configured, requests must also pass signature verification. The trigger must be enabled and the Automation must be Active before a valid request starts a run. Store webhook URLs and signing secrets securely, and regenerate them if they are exposed.Manual start#
Use Run now to start an Automation directly. This is useful for testing instructions and assignee availability before depending on recurring or event-based triggers.Runs and health#
Automation health summarizes the latest useful signal, such as never tested, running, healthy, skipped, or needs attention. Open the run details to inspect the trigger payload, Agent run, output, or recorded failure reason.A completed status describes the Automation run, not a promise that every downstream business outcome was correct. Review the linked task or output when the work matters.Pause, resume, or delete#
Pause an Automation to stop new triggered runs while you revise instructions, triggers, or the assigned Agent or Crew. Resume it when the configuration is ready.Delete an Automation only when its definition and run history are no longer needed. The current UI can display older Archived records, but it does not provide an action to archive an Automation.Practical safety checks#
Before relying on an Automation:2.
Confirm the Agent or Crew has the required access.
3.
Inspect the Agent run and output.
4.
Test each trigger separately.
5.
Use a narrow status or distinctive comment phrase.
6.
Keep secret webhook URLs outside source control and public messages.
Modified at 2026-08-04 04:02:55
