Configuring nodes

Every node in a Workflow stores its own configuration as part of the saved graph. When you commit, the configured DAG — including all node settings — is what the engine runs. Most nodes with non-trivial settings open a dedicated configuration modal when you interact with them.

How configuration is saved

When you confirm a modal, EzFlow writes the settings into the node's data in the editor state, recalculates the node's input and output handles, and cascades those updates to any downstream nodes. This keeps handle types consistent across the graph. The changes are part of your working edits until you commit.

Opening a node's configuration

Click the node card on the canvas. Nodes that support inline editing — such as Value and Comment — let you edit directly on the card. All other nodes open a configuration modal.

Configuration by node type

Cron Trigger

Set the schedule using a cron expression (minute, hour, day of month, month, day of week). The modal includes helpers for common intervals.

See Cron Trigger.

HTTP Trigger

EzFlow generates a unique webhook URL for each HTTP Trigger node. The modal lets you configure body parsing options and authentication so the engine validates incoming requests correctly.

See HTTP Trigger.

Script

Opens a full Monaco editor pre-configured for TypeScript. Write a function that receives the node's inputs and returns its outputs. Type definitions are loaded automatically.

See Script.

HTTP Request

Configure the outbound HTTP call: method, URL, query parameters, headers, authentication type (none, Basic, Bearer), and request body. A separate tab lets you define how the response is parsed.

Mapper

Define a list of field-mapping rules. Each rule specifies an input key (the field name coming in), an output key (the field name going out), and the data type. Add rows with the + button and save when done.

See Mapper.

Wait for Event

Configure the external event or webhook this node waits for before the Workflow resumes. The modal exposes the event identifier and timeout settings.

See Wait for Event.

LLM Completion

Select the LLM provider (the available providers depend on the API keys configured in your account), the model, and the prompt. System and user prompt fields both support variable expressions so you can inject upstream data.

See LLM Completion.

Object Merger and Chained Conditions

Both open dedicated modals with structured editors for defining how objects are merged or how condition chains are evaluated. Confirm to save.

After configuring

Once you have set up your nodes and wired their edges, commit the Workflow so the engine picks up the changes. See Variables & data to learn how node outputs flow to downstream inputs.