Scheduled Sume runs: cron or API trigger is fixed at create

A Sume Action is either cron or api triggered, chosen at creation. How to author one, why you cannot create it over the public API, and how to run the api kind.

5 min readSume
All posts

An Action has a trigger_type of cron or api, and it cannot be changed after creation. Authoring happens in the dashboard at sume.com/agents/scheduled; there is no create or edit endpoint in the public API, and no MCP tool or CLI command for it. What the API does expose, under /v1/actions with aut_ ids, is running and reading Actions with the actions:read and actions:write scopes.

Only an api Action can be started on demand. Call POST /v1/actions/{handle}/{slug}/runs and poll /v1/action-runs/{id}. Team-owned Actions are not reachable over the public API.

Cron versus api

Action trigger types per Sume docs (read 2026-10-03)
TriggerStarts whenPublic API start
cronOn its scheduleNo
apiYou call the run endpointYes

Errors you will meet

Calling the run endpoint on a paused Action returns 409 action_inactive; on a cron Action it returns 409 action_api_trigger_disabled. Runs are not jobs, so poll the run, and note that events_url is always null for Action runs.

Sources

Related posts

More in Agents

All Agents posts

Written by Sume