Flow nodes and execution rules
Choose the right step for your flow. See which nodes show content, change data, or choose a path, and when visitors stop or continue.
Nodes are the steps that let your flow ask questions, show offers, change data, and choose what happens next. A flow runs them in order along the selected path. Some nodes end that path, so visitors won't necessarily reach every step you can see below them on the canvas.
When to use it
Choose a node based on what you want to happen at that point in the flow. Use display nodes to show something, action nodes to do something, and routing nodes to choose a path.
For example, WorkForge (opens in a new tab) could start with a Condition that checks the current page. The matching path asks a planning question, saves a variable, and shows a form. The other path exits. After submission, the form shows a confirmation or redirects to a real page.
Each step has a separate job. The Condition doesn't ask the question, saving the variable doesn't submit the form, and showing a confirmation doesn't send the promised email.
Settings
Display nodes
| If you'd like to… | Choose | Reference |
|---|---|---|
| Ask a new or shared question when question handling permits | Question | Question and Router |
| Show a reusable form with its submission action | Form | Offer and Form |
| Show a reusable promotion or call to action | Offer | Offer and Form |
| Show rich-text content that ends a form's post-submit path | Message | Submit Message |
| Place supported app content on the page | A connected app, such as Senja | Connected app embed |
Forms and offers are shared items, not separate copies inside each flow. A form's post-submit path is separate from the ordinary path through its parent flow.
Action nodes
| If you'd like to… | Choose | Reference |
|---|---|---|
| Send visitors to another page | Redirect | Redirect |
| Run JavaScript, or display the content it returns when supported | Code | Code node JavaScript API |
| Adjust scores, save variables, assign segments, or make supported email-platform updates | Set Data | Set Data |
| Send an HTTPS request through the webhook service | Webhook | Webhook |
System flows show more specific data-action labels, such as Set Score and Set Variable. Field and tag actions depend on your connected integration. Webhook availability depends on your plan's feature access.
Routing nodes
| If you'd like to… | Choose |
|---|---|
| Follow Yes or No based on a rule | Condition |
| Use an existing answer or segment without asking | Router |
| Assign visitors to equal random groups and remember their assignment | Split |
| Compare configured scores, with an ordered priority for ties | High Score |
| End the flow and dismiss its widget | Exit Flow |
High Score can choose the highest or lowest configured score. It appears when the current flow has at least two score names, or the project's flows define at least two variable names. Its node reference explains score and variable modes, default routes, and comparisons.
The A/B Test insertion item is coming soon. Use the separate whole-flow A/B testing feature to run a live test.
New-node defaults
| New node | Starting settings |
|---|---|
| Question | No selected question or answer routing |
| Form or Offer | No selected library item |
| Router | No selected group |
| Condition | Empty Yes and No paths and an empty OR rule, which matches nobody |
| Split | Two empty groups |
| Message | Thank you! |
| Set Data | Unnamed score adjustment of 1 |
| Webhook | POST, once-per-visitor delivery, and no destination URL |
How visitors move through it
Branches can rejoin shared steps if nothing in the branch ends the route. Forms, offers, messages, exits, and navigation can stop it. The canvas dims unreachable nodes and disables their drop zones.
Put actions before the node that ends the path they support. A Code node that displays returned content behaves differently from code that only runs an action. The Code node reference explains when it continues.
A form has its own post-submit path
A form doesn't resume ordinary steps below it after submission. Use Post-Submit Actions For This Form for its message or redirect. See form completion.
The post-submit insertion menu excludes forms, offers, asking questions, and Exit Flow. Message is available in that post-submit path, not the ordinary parent path. Put supported data actions and routing before the final message or redirect.
Things to know
Widget targeting decides whether a regular flow can appear. Question handling decides whether visitors are asked questions they've already answered. A system flow runs without those widget controls.
You can't insert unavailable or locked nodes through the insertion menu. A configured node can still do nothing if the visitor never reaches it, required data is missing, or an external destination rejects its action.
Preview each branch, then test the actual widget or system flow. If someone takes the wrong path, flow routing troubleshooting helps you find the first decision that differs from what you intended.