The Flow Builder is the canvas where automation flows are designed. It presents a node-based graph interface — each step in the flow is a node, nodes are connected by edges that represent execution paths, and the full flow is stored as a structured JSON object ofDocumentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
nodes and edges arrays. Every node has a visual position on the canvas that reflects the logical sequence of the flow.
Building a flow means placing nodes, connecting them in order, configuring each node’s settings, and activating when the flow is ready.
What this covers
- The Flow Builder interface and canvas layout
- Node types and how they connect
- How flows are stored
- Activating and deactivating flows
- AI-assisted flow creation via Galantis AI
Opening the Flow Builder
Navigate to Automations
In the Galantis dashboard, go to Automations and click New Automation, or open an existing automation to edit its flow.
The canvas opens
The Flow Builder canvas loads with an empty canvas or the existing flow. A
TriggerNode is always present as the entry point — it cannot be removed or repositioned to a non-entry position.Add nodes
Drag nodes onto the canvas from the node panel or click the
+ connector on any existing node to add a new step. Connect nodes by drawing edges between them.Configure each node
Click any node to open its settings panel. Configure the trigger event, delay duration, condition logic, or template assignment depending on the node type.
Node types
Every flow is built from four node types. Each type has a specific role in the execution sequence.- Trigger Node
- Delay Node
- Condition Node
- Action Node
TriggerNode is the entry point of every flow. It defines the event that starts the automation and accepts exactly one trigger per flow.Every automation has exactly one
TriggerNode — it cannot be duplicated or placed mid-flow. The trigger fires when a qualifying event occurs for a customer, enrolling them into the flow from this point.Configuration includes:- The trigger event type (see Triggers for all available options)
- Whether to include existing users who already match the trigger condition at activation time (
include_existing_users)
TriggerNode connects to the first step in the flow — typically a DelayNode or ConditionNode.How flows are stored
Flows are stored as structured JSON with two arrays:nodes— an array of node objects, each with a type, configuration, and canvas positionedges— an array of connection objects defining which node connects to which
Flow validation
Before a flow can be activated, Galantis runs a set of validation checks:| Check | What is validated |
|---|---|
| Template approval | All Action nodes use APPROVED templates |
| Node connections | All nodes are connected — no orphaned nodes |
| Condition branches | Both YES and NO branches of every Condition node connect to a subsequent node |
| Condition completeness | All condition logic is fully configured with no empty fields |
| Frequency cap configuration | Frequency cap is set and valid |
Activating and deactivating flows
Toggle the automation status between Active and Inactive from the automation detail page. Deactivating a flow stops new customers from being enrolled. Customers already in the flow at the time of deactivation continue through their remaining nodes — deactivation does not cancel in-progress executions.Galantis AI assistance
The Flow Builder includes AI-powered assistance via Galantis AI. When building or editing a flow, Galantis AI can:- Suggest appropriate triggers and action sequences based on a goal you describe
- Highlight incomplete or conflicting node configurations
- Surface optimization suggestions — for example, flagging a missing delay in an abandonment recovery flow
Related guides
- Triggers — All trigger events and their configuration
- Conditions — Condition types, operators, and branching logic
- Actions — Action and Delay node configuration
- Activity Tracking — Monitoring flow execution per customer