Trigger Automation
Fires an Automation flow from within a Conversational Flow or Handler, running background tasks without interrupting the user-facing conversation.
The Trigger Automation node fires a specific Automation from within a Conversational Flow or Handler. Automations normally run at lifecycle events (like end of conversation), but Trigger Automation lets you run them at any point during a conversation – enabling background tasks like logging, summarization, or external notifications without interrupting the user-facing experience.
Configuration
Automation
Select which Automation to trigger. The dropdown lists all Automations defined in the current pipeline.
When to Use
- Log a milestone – Trigger a logging automation when the user reaches a key step (e.g., completes a form, selects a product)
- Background data enrichment – Fire an automation that fetches or processes data without making the user wait
- Non-blocking webhook – Send a notification to an external system without pausing the conversation flow
- Mid-conversation summary – Generate a partial summary or title at a specific point, not just at conversation end
Behavior
Trigger Automation fires the automation and continues immediately to the next node in the current flow – it does not wait for the automation to complete. The automation runs asynchronously in the background.
This means the user continues having a conversation normally while the automation executes in the background.
Typical Pattern
Collect User Data (email)
│
└──► Store Variable (→ {{variable.email}})
│
└──► Trigger Automation (LogLeadCapture) ← runs in background
│
└──► Text ("Thanks! We'll be in touch.") ← user sees this immediatelyBecause Trigger Automation is non-blocking, do not use it for tasks whose output is needed by subsequent nodes in the same flow. If you need the automation's result before continuing, consider using a Call Webhook node with a synchronous request instead.