Skip to main content
External systems start workflows without Workflow Studio. They use explicit start params on the trigger or request — the same shape as Manual Run.

Current model (2026-06-28)

Saved defaults (run_setup_json) pre-fill Studio forms only. They are not merged at fire time. At runtime the engine resolves:
  1. Canvas step config (graph)
  2. Start params sent with the command or stored on the trigger (trigger_payload, trigger_steps, excluded_step_ids)
See Run setup for Save defaults, Manual Run, and field overrides.

Legacy merge rule (deprecated)

External triggers previously used:
Default: merge on unless use_run_setup_defaults: false. Deprecated 2026-06-28. New schedules and integrations should send full start params explicitly. Existing deployments may still merge until migrated — contact support if you’re unsure whether your integration is affected.

Inbound webhooks

  1. Sender POSTs to /v1/inbound-webhooks/{subscription_id} with HMAC + idempotency key.
  2. BFF maps JSON body → trigger_payload and applies subscription extras.
  3. Engine starts with POST body + extras + graph — not merged from saved run_setup_json.
Subscription extras (start params at fire time):
Studio pre-fills the Inbound editor from saved defaults; fire time uses what is stored on the subscription and in the POST body.

Platform events (workflow_triggers.type = platform_event)

AgentRuntime starts workflows when tenant platform events fire — no partner execute call. Configure in Workflow Studio → Run setup → Events. Each event carries run identity (external_user_id, connection_id, …) — there is no Manual Run as on this tab. Optional segment_id limits runs to principals in that segment. See Triggers and run identity. REST: same trigger CRUD as cron — GET/POST/PATCH/DELETE /workflows/{id}/triggers with "type": "platform_event". Example config (Embedded Connect bootstrap on connect — Composio link uses composio_account):
At fire time the platform sets run.external_user_id from the event and exposes connection fields under platform_event / start params. MCP steps with connection_resolution: principal resolve automatically. Supported events (v1): principal.created, connection.created, connection.revoked, principal.suspended, principal.deleted.

Cron (workflow_triggers)

AgentRuntime runs the schedule and dispatches the trigger automatically. REST: GET/POST/PATCH/DELETE /workflows/{id}/triggers. Target schedule config (same Start steps model as Manual):
For Embedded Connect graphs, set Run as → Segment in Studio so segment_id is stored — one run per principal per tick. See Triggers and run identity. Legacy shape (do not use for new schedules):
Studio Cron tab exposes schedule wiring and start inputs prefilled from workflow saved defaults.

API / command start

Send complete start params — no reliance on saved defaults at runtime: