Workflow Node Rules and Validation

What the icons mean

On the workflow canvas, nodes can show a red or orange/amber icon. Click the icon to see the list of issues.

• Red (errors) – Blocking. The workflow may not publish or run until these are fixed. Address every error on the node.
• Orange (warnings) – Not blocking; the workflow can run, but behavior may be incomplete or unclear. Fix warnings for predictable results.

Trigger rules (errors)

Each trigger type has required settings. If missing, the trigger node shows errors:

• API – HTTP method is required; must be one of GET, POST, PUT, PATCH, DELETE.
• Form – A form must be selected.
• Webhook – Platform, webhook secret, and a sample payload (valid JSON) are required.
• Scheduled – Schedule type (min, hour, day, week, month) and interval are required. Interval must be in the allowed range: min 15/30/45; hour 1/2/3/4/6/8/12/23; day 1/2/3/7/14; week 1/3/7; month 1/3/7/12. Specific-time schedules instead pick an hour of day, day of month, or month of year.
• Workflow – The workflow that triggers this one must be selected.
• Playground – A playground and one of its trigger @keys must be selected.
• Agent – No settings required. The workflow becomes a tool an AI agent can call; define the input fields the agent supplies as arguments, then attach the workflow to the agent and pick this trigger.
• Any required trigger input must have a default value (or the trigger shows an error).

Task rules (errors)

Tasks show errors when required configuration is missing:

• Platform Tool – Action required; selected action must be valid; all required inputs must be provided; for OAuth tools, a connection must be selected.
• AI Model – An AI model must be selected; if custom outputs are enabled, at least one output field is required.
• Code – Code and at least one output field are required.
• Template – Template content and a valid output type are required.
• Data Visualizer – A visualizer must be selected.
• Trigger Inputs – At least one output mapping is required.
• Approval – At least one assignee must be selected, and the minimum approval count must be in [1, assignees] (auto-clamped in the builder). Approval tasks are always treated as required — the Optional-task toggle is hidden in the drawer, and the engine ignores is_optional on approval nodes.

Task rules (warnings)

These do not block runs but indicate incomplete setup:

• Condition – Connect the Yes and/or No branch to the next steps. Connecting both is recommended.
• Loop – Connect the loop start task and set max iterations (1–20).
• Parallel – Add at least one parallel branch task.

How to fix

Open the node (trigger or task) in the builder, fix the listed items in the error/warning list, and save. For configuration details, see Workflow Triggers and Workflow Task Types.