Run an agent on a schedule
Schedule an AI agent with cron: run it every morning, once at a set time, or on a signed webhook, and read each run's result. CLI, MCP and API steps.An automation sends a message to one of your Cloud agents on a schedule: a five-field cron expression, a single time, or a signed webhook. Each firing starts a run, and you can read its status afterwards.
With the CLI
Section titled “With the CLI”Create the agent the automation will run, then the automation:
AGENT=$(dexto cloud agents create --name "Morning digest" \ --instructions "Summarize the top three stories about AI agents, with links." \ --tool web_search --tool web_fetch --json | jq -r '.id')
AUTOMATION=$(dexto cloud automations create --name "Morning digest" --agent "$AGENT" \ --message "Write today's digest." --cron "0 8 * * 1-5" --timezone Europe/London \ --json | jq -r '.id')The cron is read in UTC unless you pass --timezone. Use --at 2026-12-01T09:00:00Z to fire once,
or --webhook to fire on each signed request to the URL it prints. Each firing starts a new
session; pass --session to send them all to one.
Try it now instead of waiting, then read what happened:
dexto cloud automations run "$AUTOMATION"dexto cloud automations firings "$AUTOMATION"firings lists each firing, newest first, with its run’s status. Pause and resume a schedule with
dexto cloud automations pause and dexto cloud automations resume.
With MCP
Section titled “With MCP”A client can do all of this over MCP: dexto_cloud_automations_create,
dexto_cloud_automations_run, dexto_cloud_automations_firings, dexto_cloud_automations_pause
and dexto_cloud_automations_resume, with dexto_cloud_agents_create for the agent. Changes are at
the act level, so your client asks you before each one.
The Dexto app’s own recurring work (Loops on your Dexto computer) uses dexto_automation_create
instead; see Loops.
With the HTTP API
Section titled “With the HTTP API”curl -X POST https://api.dexto.ai/v1/automations \ -H "Authorization: Bearer $DEXTO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Morning digest", "trigger": { "type": "schedule", "schedule": { "type": "recurring", "cron": "0 8 * * 1-5", "timezone": "Europe/London" } }, "target": { "type": "agent", "agent_id": "'"$AGENT"'", "message": "Write today'\''s digest." } }'See the Automations API for webhooks, signing secrets and firing history.
An automation is free; each firing’s run is charged like any other run of the agent: its model tokens and any paid tools it uses.