Routes Node
Routes Node
The Routes Node is one of the main components of a Spaceflow workflow. It lets you direct flow execution through different paths based on the conditions you define.
What is the Routes Node?
Instead of following a single linear path, the Routes Node lets you build dynamic flows where each execution can take a different direction depending on the data. Use it to:
- Evaluate conditions at a specific point in the flow
- Decide which path the flow should follow
- Handle multiple possible outcomes from a single node
How does it work?
When you add a Routes Node to your flow:
- You define one or more routes (for example, Route 1, Route 2, Route 3).
- For each route, you configure one or more conditions.
- During execution, the system evaluates the conditions and directs the flow to all valid routes. If no condition is met, the flow follows the fallback route.
Node structure
Inside the configuration panel, you'll find the following sections:
Node Name
A text field to identify the node within your flow. Use a clear and descriptive name so it's easy to locate.
Route Conditions
This is where you create and manage your routes:
- Each route (Route 1, Route 2, Route 3…) represents a possible path.
- Click + Add Route to create a new route.
- You can also remove existing routes that are no longer needed.
Fallback Route
The fallback route is an alternative path that is executed when no condition is met. It prevents the flow from breaking or stopping unexpectedly.
Practical example
Imagine an approval flow based on the request value:
| Route | Condition | Action |
|---|---|---|
| Route 1 | Value less than $1,000 | Automatic approval |
| Route 2 | Value between $1,000 and $5,000 | Send to manager |
| Route 3 | Value above $5,000 | Send to director |
| Fallback | Invalid data | End flow |
In this scenario, the Routes Node automatically decides which path to follow based on the value.
When to use
Use the Routes Node whenever you need to:
- Create decision points in your flow
- Separate different scenarios into distinct paths
- Automate business rules
- Avoid duplicating entire flows for each variation
Best practices
- Name your routes clearly. Use descriptive labels like "Low value" or "High priority" so anyone reading the flow understands each path immediately.
- Always test all paths. Make sure every possible execution — including the fallback — has a defined destination. This prevents flows from stopping unexpectedly.