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:
- Canvas step config (graph)
- Start params sent with the command or stored on the trigger (
trigger_payload,trigger_steps,excluded_step_ids)
Legacy merge rule (deprecated)
use_run_setup_defaults: false.Inbound webhooks
- Sender POSTs to
/v1/inbound-webhooks/{subscription_id}with HMAC + idempotency key. - BFF maps JSON body →
trigger_payloadand applies subscriptionextras. - Engine starts with POST body + extras + graph —
not merged from saved.run_setup_json
extras (start params at fire time):
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):
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):
segment_id is stored — one run per principal per tick. See Triggers and run identity.