Core
Routines
Automate recurring work with flows the agent builds and you control, from triggers to human approval.
A routine is an automated flow: a trigger, steps that call the agent or your connectors, conditions and, where you want it, a human approval. "Automated flows connected to your integrations."
Screenshot
The routine list
Open the Routines page. The list has a search box ("Search routines...") and the filters All, Running, Succeeded, Failed and Cancelled. Each routine shows its status, a scope (Organization or Team), its Next run and its Last run. A health line summarises the success rate and average duration of recent runs. With no routines the page says "No routines yet. Ask the agent to create one." You can also start from a marketplace template.
In short
Try it
In the agent chat, write for example "Every Monday, check open tasks and notify me".
Open Routines and click the new routine.
Read the flow on the canvas, then press the play button to run it once.
Good to know
- Routines may be missing on an instance: "Routines are unavailable right now."
- Cancel a running routine with Cancel run; a failed one can be restarted.
The canvas editor
A routine opens as a graph. Right-click the canvas (hint: "Right-click to add") or use Add element and Search capabilities... to add elements. Auto-arrange tidies the layout, and you can choose the flow direction. The element groups are:
| Group | Elements |
|---|---|
| Steps | Agent step, Connector call (one per connector you have), Notification, Condition, Transform |
| Logic | Decision, Switch, Human approval |
| Triggers | Schedule (cron), Delay, Interval, Event trigger, Webhook, Timer, One-time trigger |
| Risk | Risk assessment, Risk matrix, Mitigation |
| Controls | Poll until, Retry, Repeat every |
Human approval pauses the routine until a person approves: "the human stays in control". The One-time trigger fires once when a condition holds: a fresh organization, a new team, a new member or low activity. Elements pass data on as placeholders (Trigger, Status, Result).
Good to know
- Edit an element's name and description with Edit element. Changes that could not be saved say "Change could not be saved".
Activate or keep as draft
A routine is either Draft or Active. "Activating arms the scheduler and the inbound webhook so this routine runs automatically on its triggers." Disabling disarms both, and you can still run the routine manually with the play button. A webhook routine shows its Webhook URL to copy.
In short
Runs and settings
Run settings let you set Max steps, Max visits per node, a Timeout (s) and an optional Run key, which de-duplicates runs with the same key. Run once completes the routine after one success. A Deadline (hours) sends a notification when a run takes longer, and the run keeps going. Start run begins a run, Cancel run stops it.
The Runs history lists every run with its status (Pending, Running, Success, Error, Cancelled, Rejected or Paused) and a Timeline of the steps with what was received and produced.
Good to know
- Copy a run's id to refer to it in a support request.
- Settings has a Routines page that lists your organization's flows and links here. See Settings.