Node Configuration

Each node has a configuration panel where you set its parameters. The available fields depend on the node type.

Opening the Configuration Panel

Click on any node in the canvas to open its configuration dialog. The panel shows:

• Node title — editable name for the node
• Configuration fields — type-specific settings (queries, field mappings, URLs, etc.)
• Settings tab — execution mode and error handling options

Field Types

Node configuration uses dynamic forms with various field types:

Field Type	Description
Text	Single-line text input
Textarea	Multi-line text input
Number	Numeric input
Select	Dropdown with predefined options
Checkbox	Boolean toggle
Key-Value	List of key-value pairs (e.g., HTTP headers)
Connection	Dropdown to select a saved connection
Upstream Property	Select a field from an upstream node's output
Condition Group	Rule builder for conditional logic

Expressions

Many text fields support expressions — dynamic values that reference data from upstream nodes. Expressions use the {{ }} syntax:

{{ nodeName.fieldName }}

For example, if you have an HTTP Request node named "fetchUsers" that outputs user data, you can reference it in a downstream Transform node:

{{ fetchUsers.name }}

Expressions are resolved at runtime using the actual output data from upstream nodes.

Conditional Fields

Some fields only appear based on other settings. For example:

• The Join Type field on a Merge node only appears when the merge mode is set to "Merge by Key"
• Authentication fields on an HTTP Request node only appear when an auth type is selected

Settings Tab

Every node has a Settings tab with common execution options:

Execution Mode

For streaming nodes, you can choose between:

• Piped (default) — items stream immediately to downstream nodes as they're produced
• Gated — all items are collected before downstream nodes execute

Gated mode is useful when downstream nodes need the complete dataset before processing.

Error Outputs

• Enable Fallback Output — routes validation errors to a fallback handle instead of failing the node
• Enable Failed Output — routes execution errors to a failed handle instead of failing the node

These allow you to build error handling paths in your workflow rather than having the entire workflow fail.