Skip to main content
Run setup controls how a workflow starts from Studio. Saved defaults pre-fill forms; runtime uses canvas config plus explicit start params.

​
Saved defaults (run_setup_json)

  • Save defaults in Workflow setup → Manual tab persists start steps and inputs to run_setup_json.
  • Used to pre-fill Manual, Cron, and Inbound forms.
  • Not merged at fire time — Manual Run and triggers send explicit params.

​
Manual Run

  1. Open Workflow setup → Manual.
  2. Choose Start steps (unchecked auto roots → excluded_step_ids for that run).
  3. Set Starting input / per-step overrides.
  4. Run sends the current form — it does not update saved defaults.
  5. Cancel reverts the form to the last Save defaults snapshot.

​
Cron schedules

Workflow setup → Cron (or Operate → Schedules):
  • Same start step picker and per-step overrides as Manual.
  • Values are stored on workflow_triggers.config when you add the schedule.
  • Each fire uses that config + canvas — not run_setup_json.

​
Inbound webhooks

Workflow setup → Inbound:
  • Optional static start params saved on subscription extras.
  • POST body at fire time is merged with those extras (POST wins on conflicts).

​
Field editor (canvas-first)

  • Node sidebar is the primary place for step inputs (prompts, MCP tool_args, etc.).
  • Setup shows those values in editable fields, pre-filled from the canvas (and saved defaults).
  • Edit inline to override for this run or Save defaults (overrides-only snapshot).
  • Include checkbox: unchecked → omit key from start params (canvas used at runtime).
  • Cleared field ("") while included → sends explicit empty; Use step value reverts to canvas (shown only after you override).
  • While Setup is open, non-edited fields track canvas changes; edited fields stay until revert.