Every node on the canvas has a Node Inspector — a configuration panel that appears in the right pane when you click on a node in Edit mode. This is where you define what each step does.
Clicking away from all nodes or pressing Escape collapses the inspector back to the canvas overview.
Every inspector follows the same structure:
Many input fields accept data from earlier steps, not just static values. To bind a field to a step output:
This is how you thread data through a workflow: the output of Step 2 becomes the input of Step 4.
See How to connect a form field to live data with binding chips for a detailed walkthrough.
Each node type has its own inspector fields. Examples:
| Node | Key fields |
|---|---|
| Start (Trigger) | Trigger type, schedule, webhook URL, filter conditions |
| Human in the Loop | Linked form, assignment rule, task type |
| Google Sheets Writer | Spreadsheet, sheet, write mode (row / column) |
| PDF OCR Reader | File source, page range, AI model, temperature |
| Web Search | Query, engine (Google / Bing / News), result count |
| Branch / Decision | Condition expression for each output branch |
| Loop | Iterator source, loop body, exit condition |
If a node has missing or invalid configuration, a red error indicator appears on the node on the canvas. The inspector highlights the specific field(s) that need attention. You cannot publish a workflow with validation errors.
When you switch to Play mode, clicking a node shows its last run output instead of its configuration. Switch back to Edit mode to make configuration changes.
