Activate Flow
Directly triggers a specific Conversational Flow from within a Handler, bypassing normal flow routing.
The Activate Flow node triggers a specific Conversational Flow directly from within a Handler. Unlike Continue Processing (which hands off to whatever flow is currently active or determined by Core or Main flow logics), Activate Flow explicitly selects which flow to run next.
Available in: Handlers only.
When to Use
Use Activate Flow when a Handler's pre-processing determines that a specific flow should handle the event – regardless of which flow was previously active.
Common scenarios:
- On conversation-start → Activate the
Greetflow to send an opening message - On face-detected → Activate the
Greetflow to proactively greet an approaching kiosk user - Variable-based routing → Check a variable in the Handler (e.g., GDPR consent) and activate the appropriate flow based on its value
Configuration
Select Flow
Choose which Conversational Flow to activate. The dropdown lists all flows defined in the current pipeline.
Reset Flow Stack
Controls what happens to the flow stack when the activated flow ends.
- On – the flow stack is cleared before the flow is activated. When the activated flow ends, there is nothing to return to – the conversation simply waits for the next user input, as if starting fresh.
- Off (default) – the activated flow is pushed onto the existing flow stack instead of replacing it. When it ends (via
End Flow), control returns to whichever flow was on the stack before it.
Behavior
- The selected flow is activated immediately when this node is reached
- The Handler finishes – no
Continue Processingis needed afterActivate Flow - The activated flow runs as if it had been triggered normally by user input
- Whether it starts with a clean flow stack or preserves the existing one depends on Reset Flow Stack above
Contrast with Go to Flow
Both nodes redirect execution to another flow, but they operate in different contexts:
| Activate Flow | Go to Flow | |
|---|---|---|
| Available in | Handlers only | Conversational Flows |
| Context | Pre-processing (before flows) | Mid-conversation (within flows) |
| After the flow ends | Handler pipeline ends | Returns to caller (or ends, depending on stack) |
Typical Patterns
Greeting on conversation start:
Signal Handler (On conversation-start)
└──► Activate Flow (Greet)GDPR gate in On User Input:
Text Handler Entry → On User Input
└──► Check Variable (gdpr)
├── equals true ──► Continue Processing
└── else ──► Activate Flow (GDPRConsent)