Skip to content

Configuring nodes

Click a node and its panel opens on the left of the canvas. That's where you set its fields, see its data and change how it handles errors. The fields change per node type, but the patterns are the same everywhere.

The node panel for an HTTP Request node open on the left of the canvas, Settings tab selected, with an expression in the URL field and the expression icon next to the URL label.The node panel for an HTTP Request node open on the left of the canvas, Settings tab selected, with an expression in the URL field and the expression icon next to the URL label.

Anatomy of the node panel

  1. Header: the node's icon and name, plus Dock panel and Close. Double-click the name to rename the node.
  2. Tabs:
    • Settings: the node's fields.
    • Schema: the node's last output as an expandable tree. Drag any field from here into an input.
    • JSON: the node's last output as raw JSON.

Until the node has run, Schema and JSON say Run the flow to see output data.

For a node inside a loop, the data view shows one iteration at a time (Iteration N of M).

Docking several panels

By default, clicking a different node replaces the open panel. Click Dock panel to keep a panel open. The next node you click opens in a new panel beside it.

  • You can dock up to 5 panels.
  • Drag a docked panel by its header to reorder it.
  • Drag a panel's right edge to resize it.
  • Click Undock panel to release it, or Close to close it.

Docking is useful when you're wiring an expression from one node into another and want both in view.

Field types

Text fields

Type a literal value, an expression, or a mix of both.

Long text and code fields

Multi-line, for SQL, code, AI prompts and similar.

Numbers, toggles and sliders

Standard inputs.

Some dropdowns load their options live from a connector once you pick a credential, for example the channels in your Slack workspace. A dependent dropdown waits until the field it depends on is filled in. Use the refresh button to reload the options.

Credential picker

Any node that signs in to an outside service has a credential picker. It lists the credentials in your current workspace that fit the node. You can add a new credential from the picker. See Managing credentials.

Repeating rows

List-shaped fields, such as an If node's conditions or an HTTP node's headers. Add a row to append; the trash icon removes one.

Additional properties

Less common options sit under an Additional properties expander.

Static values and expressions

Every text-like field can hold:

  • A static value: what you type is used as-is.
  • An expression: wrapped in {{ }} and resolved when the node runs.

Mix them freely:

https://api.example.com/users/{{ $trigger.payload.id }}/orders?status={{ $node["Filter"].output.status }}

Expressions only look values up. They don't run functions or arithmetic. Do that in a Set, Data Transform or Code node, then reference its output. See Expressions.

Drag a field in

Open the upstream node's panel on the Schema tab, then drag a field into the input you're editing. Flero inserts the matching expression, for example {{ $node["Fetch user"].json.email }}. Docking both panels makes this easy.

The Expression Builder

Click the <> icon next to a field's label to open the Expression Builder. It shows the data available from upstream nodes and the trigger. Pick a field to insert its expression, then click Apply Expression.

The Expression Builder dialog open over the URL field: available data from earlier nodes, trigger data and variables on the left, the expression editor and quick templates on the right, and the Apply Expression button.The Expression Builder dialog open over the URL field: available data from earlier nodes, trigger data and variables on the left, the expression editor and quick templates on the right, and the Apply Expression button.

Node settings

Every node has engine settings that control what happens when it fails. Hover over the node and click More in its toolbar to open Node Settings.

Setting What it does
Error Mode Stop Execution (default): the run fails. Retry with Backoff: try again. Use Fallback Value: carry on with a value you set. Continue Anyway: carry on past the failure.
Retry Count With Retry with Backoff: how many times to retry (0 to 10).
Retry Delay (ms) With Retry with Backoff: the first wait. The delay doubles on each attempt.
Fallback Value With Use Fallback Value: the output to use instead. JSON, text or an expression.
Timeout (ms) Fail the node if it runs longer than this. Leave empty for no limit. You can always end a running node with Stop.
Priority Higher-priority nodes run first when branches run in parallel.

Click Save. See Retries & error handling.

AI Agent slots

The AI Agent node's panel shows three boxes: Guardrails, Memory and Tools.

  • Guardrails and Tools: drag a node from the palette onto the box. Flero adds the node to the canvas near the agent (tools below, guardrails above) and connects it to the agent. The box shows the icons of what's connected.
  • Memory: click to turn the agent's memory on or off.

Guardrails accept guard nodes only (AI Guardrails, Token Cost Guard, Output Format Guard, Rate Limiter Guard, Schema Validator Guard). Tools accept most action nodes, but not triggers, other AI Agents or memory nodes. A box turns green when it will accept the node you're dragging and red when it won't.

You can also connect tools and guards on the canvas through the agent's ports.

Pinning data

The JSON tab has Expand all, Copy JSON, Edit JSON and Pin Data. Pin Data saves the node's current output so it is reused on the next run. A badge reads Node data is pinned. You can also Edit JSON to write the data yourself. See Testing while you build.

Validation

Problems show up in two places:

  • While you build: a node with a missing or invalid required field is flagged.
  • When it runs: a node with a bad configuration fails with a clear error instead of passing on bad data. Click the node to read it.

A node that reads an unset workspace variable ($env.NAME) fails before it runs.

Tips & gotchas

  • Empty isn't the same as default. A blank field means "no value". Check the field's hint or the node's docs for its default.
  • Output data is from the last run. It doesn't update as you type. Run again to refresh it.
  • Renaming a node breaks expressions that use its old name. Update them after a rename.
  • Credentials are per workspace. If you can't find a credential, check you're in the right workspace.

Found something out of date? This page lives in the Flero docs content set.