A text box for the workflow’s parameters, written as JSON — a simple
{ "field": "value" } format. Every workflow needs at least a
domain_id; several need more. Example for a technical audit:
This must be valid JSON — curly braces, double quotes around field
names and text values, commas between fields, no trailing comma. If it
doesn’t parse, you’ll see “Inputs must be a JSON object” and can’t
submit until it’s fixed. Copy the exact examples on each
workflow’s own page
and just swap in your own values.
Leaving Inputs completely empty is allowed — some workflows have every
field optional with sensible defaults, though most real ones need at
least domain_id.
Success: a green confirmation toast appears, the dialog closes, and
you land on the Workflows list. Your new run appears there —
usually within a few seconds, occasionally up to about 30.
Failure: a red toast appears with a reason (for example, a missing
required field, or an invalid domain ID). Fix the issue and try again —
nothing was created.
The run doesn’t appear instantly because triggering just hands the
request to the workflow engine — the actual run row is created moments
later. If you don’t see it within a minute, refresh the Workflows page.
The workflow engine takes over: it works through the workflow’s steps —
some one after another, some in parallel — dispatching each one to the
right AI agent. You don’t need to do anything else unless the workflow
reaches a human approval step (content workflows always do, right
before publishing).
