Work in the Flow Builder

The Flow Builder shows the nodes and connections behind an action. Use it to make the execution path easy to read, test, and maintain.

Build a connected path#

Open Workflows → Go to Flow Builder and select the controller and action. For a released action, enter its editable draft before changing nodes.

1. Add a node from the library.
2. Give it a name that describes its result, such as FetchCustomer or OrderResponse.
3. Configure its inputs and operation.
4. Set the action's entry node and connect the outgoing execution path.
5. Save and test the workflow.

Placing nodes next to each other does not make them execute. The action needs an entry node, and each subsequent step needs an execution connection. A disconnected node can remain visible on the canvas without participating in a request.

Name nodes as data contracts#

Successful node outputs are available to later nodes by name, for example ${FetchCustomer}. Renaming a node can therefore break downstream templates even if the visual connections remain intact. Search its uses before renaming it.

Prefer one clear responsibility per node. Separate authentication, input validation, external calls, and response shaping so failures are easier to locate.

Branch intentionally#

A Condition has true and false paths. A Decision evaluates configured rows and takes the first matching branch. Label and test every outcome, including the case where no decision row matches.

Notes, headings, and other visual annotations help explain intent but are not business execution steps. Keep the main path readable and place background work where its relationship to the response is clear.

Save, inspect, and test#

After rewiring, run a representative request and inspect the executed node sequence. Check that the expected final node produced the response and that branches did not skip authorization or validation.

Use debugging for a failing path and execution behavior for details about termination and background work.