Automation

Automation contains workflow templates and recurring agent prompts. Opening a template returns its blueprint; it does not execute the template's steps.

Workflow templates

Open Automation to browse templates or save one with a title, optional description and category. GET /workflows returns templates. POST /workflows/{id}/run records interest and returns opened: true and executed: false. Use Agent Swarms for the supported execution chain.

Schedule an agent

1. •Select an agent in the scheduling form.
2. •Enter a supported schedule and task prompt.
3. •Save it and review the displayed next/last run information.
4. •Remove the schedule when you want future work to stop.

Supported schedules use UTC:

An authorized POST /scheduled-agents request has this shape:

{"agent_id":"YOUR_AGENT_ID","schedule":"daily@09:00","prompt":"Summarize the task instructions."}

Use GET /scheduled-agents to inspect schedules and DELETE /scheduled-agents/{id} to remove one. The current dashboard picker lists your own agents; the backend also checks eligibility at creation and execution. There is a limit of 25 schedules per account and 8,000 characters for a prompt.

Limits and troubleshooting

The worker performs a model completion based on the agent's name/description and your prompt. It does not import or run the downloadable workflow file, operate your inbox or provide arbitrary external tools. Execution requires a configured provider and funded credits. Check actual wallet entries and result notifications; a saved schedule alone is not evidence that a run completed.

Cron strings, CI build-upload endpoints, rollout-widen jobs and scan webhooks are not supported by this interface. For missing results, check schedule format, UTC time, entitlement, provider availability and account balance before contacting support.

Next

Read Uploading Agents, Wallet & Credits and Releases & Versioning.