---
title: "How to configure Start node triggers"
description: "Overview of instructions for configuring all Start node trigger types in Scenario Builder."
---

# 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](/en/scenariobuilder/how-to/configure-start-node-process-start.md) |
| **Webhook** | Run on HTTP request (CRM, forms, API) | [Configure webhook](/en/scenariobuilder/how-to/configure-start-node-webhook.md) |
| **Channels** | Run on message in messenger or widget | [Configure channels](/en/scenariobuilder/how-to/configure-start-node-channels.md) |
| **Internal Events** | Run on system event (ticket, new message in ticket, SLA, error) | [Configure internal events](/en/scenariobuilder/how-to/configure-start-node-internal-events.md) |
| **MCP Tool** | Call section from AI assistant (Cursor, Fastline) | [Configure MCP Tool](/en/scenariobuilder/how-to/configure-start-node-mcp-tool.md) |
| **Apps** | Run from an external application — Google Forms responses become tickets | [Receive Google Forms responses](/en/scenariobuilder/how-to/configure-start-node-google-forms.md) |

## Quick instruction selection

- **Testing or manual run** → [Process start](/en/scenariobuilder/how-to/configure-start-node-process-start.md)
- **Website form, CRM, API** → [Webhook](/en/scenariobuilder/how-to/configure-start-node-webhook.md)
- **Telegram, Viber, WhatsApp, Widget** → [Channels](/en/scenariobuilder/how-to/configure-start-node-channels.md)
- **Ticket created, new message in ticket, SLA, delivery error** → [Internal events](/en/scenariobuilder/how-to/configure-start-node-internal-events.md)
- **AI assistant calls scenario** → [MCP Tool](/en/scenariobuilder/how-to/configure-start-node-mcp-tool.md)
- **Google Forms responses should become tickets** → [Apps: Google Forms](/en/scenariobuilder/how-to/configure-start-node-google-forms.md)

## Additional materials

- **Reference:** [Internal events trigger reference](/en/scenariobuilder/reference/internal-events-trigger-reference.md) — detailed eventConfig parameters for each event
- **Explanation:** [What is the Start node](/en/scenariobuilder/explanation/what-is-start-node.md) — use cases and when to use which trigger
- **How-to:** [Create scenario](/en/scenariobuilder/how-to/create-scenario.md)
- **How-to:** [Connect AI assistant via MCP](/en/scenariodialog/how-to/connect-ai-assistant-mcp.md) — for MCP Tool
- **Integrator:** [Scenario Builder hub](/en/scenariobuilder/integrator-hub.md)
