Automations

What is an automation?

An automation is an agent run that happens on its own — on a schedule, or when something occurs in a connected service. No one needs to be watching. The agent runs, does its job, and the result shows up in Monitoring.

Every automation belongs to a specific agent. It runs that agent with its tools — the automation just decides when to fire and what prompt to start with.

Each automation has:

• An agent — the one doing the work
• A prompt — what it should do each time it runs
• A model — which AI provider and credentials to use
• A trigger — when it fires (schedule, event, or manual)

Where they live

You manage automations in two places:

• Inside an agent — open the agent and click the Automations tab in the right panel. You’ll see the automations attached to this specific agent, and you can create new ones in context.
• Settings → Automations — the org-wide list of every automation across every agent, useful for overview, audit, or housekeeping.

When to use automations

• Scheduled tasks — daily reports, data syncs, cleanup jobs
• Event-driven workflows — new order → start fulfillment, new ticket → triage, deployment → send notification
• Anything that should run without someone triggering it manually

If you want a human in the loop — reviewing actions before they happen — open the agent and chat with it directly, or use Decopilot. Automations are for work you’ve already validated and want hands-free.

Creating an automation

1. Open the agent you want to run
2. Click the Automations tab in the right panel
3. Click New automation
4. Write the prompt — what should the agent do each run?
5. Pick a model and credentials
6. Add a trigger (schedule, event, or both)
7. Activate it

Triggers

Schedule

Runs the automation on a recurring schedule. Times are in UTC.

Minimum interval is 60 seconds. If the system restarts, missed runs are caught and fired on the next cycle.

Event

Fires when a connected service publishes a matching event. You specify the connection, the event type, and optional filters — only events that match all filters trigger the automation.

Limits

• Maximum 3 runs per automation at the same time
• Maximum 10 automation runs across your organization at once
• Each run times out after 5 minutes
• Event chains are limited to 3 levels deep (prevents loops)
• Event payloads are capped at 1 MB

If the person who created an automation leaves the organization, it’s automatically deactivated.

Next: Design what your automation will run in Agents, or track results in Monitoring.