How to configure Start node triggers?
In Scenario Builder, each section has a Start node — the entry point that defines how and when the section logic runs. Below is an index of instructions for each trigger type.
Trigger types overview
| Trigger | Purpose | Instruction |
|---|---|---|
| Process start | Manual run, testing, scheduled scenarios | Configure process start |
| Webhook | Run on HTTP request (CRM, forms, API) | Configure webhook |
| Channels | Run on message in messenger or widget | Configure channels |
| Internal Events | Run on system event (ticket, new message in ticket, SLA, error) | Configure internal events |
| MCP Tool | Call section from AI assistant (Cursor, Fastline) | Configure MCP Tool |
| Apps | Run from an external application — Google Forms responses become tickets | Receive Google Forms responses |
Quick instruction selection
- Testing or manual run → Process start
- Website form, CRM, API → Webhook
- Telegram, Viber, WhatsApp, Widget → Channels
- Ticket created, new message in ticket, SLA, delivery error → Internal events
- AI assistant calls scenario → MCP Tool
- Google Forms responses should become tickets → Apps: Google Forms
Additional materials
- Reference: Internal events trigger reference — detailed eventConfig parameters for each event
- Explanation: What is the Start node — use cases and when to use which trigger
- How-to: Create scenario
- How-to: Connect AI assistant via MCP — for MCP Tool
- Integrator: Scenario Builder hub