What is the Start node?

The Start node is the mandatory entry point of a scenario section. It defines how and when the section logic is triggered: via messenger, webhook, system event, or another trigger. Each section has exactly one Start node.

Why the Start node is needed

  • Defines the entry point — the system knows which node to begin section execution from.
  • Configures triggers — you choose what starts the section: a Telegram message, HTTP request, ticket creation, etc.
  • Centralizes settings — all section triggers are configured in one place (Node Inspector), without switching to other modules.

Start node vs Entry Point

ConceptPurpose
Start nodeMain entry point of a section. One per section. Defines triggers (channels, webhook, events, MCP Tool).
Entry PointAdditional entry point for transitions within the scenario. Used when another section jumps here via Exit Point. A section can have multiple Entry Points.

Example: The "Main menu" section has a Start node with a Telegram trigger — when a user messages the bot, the dialog starts here. The "Support" section has a Start node with Internal Events (ticket created) and a separate Entry Point — for transitions from "Main menu" via the "Support" button.

Trigger types and when to use which

When you select the Start node in Node Inspector, 5 trigger types are available. Below is a short overview and recommendations.

TriggerWhen to useDetailed guide
Process startManual run, testing, scheduled scenariosConfigure process start
WebhookCRM integration, website form, external APIConfigure webhook
ChannelsBot in messengers (Telegram, Viber, WhatsApp) or widgetConfigure channels
Internal EventsAutomation based on events (ticket created, SLA, delivery error)Configure internal events
MCP ToolCalling the section from an AI assistant (Cursor, Fastline)Configure MCP Tool

Use cases: when each trigger fits

Use case 1: Bot in Telegram for customers

Situation: Customers message the bot in Telegram — the bot responds, shows a menu, accepts orders.

Trigger: Channels — select Telegram. The section runs on every user message.

Details: Configure channels. Channel connections can be configured both in the Start node and in process settings — both options change the same configuration.

Use case 2: Website form sends data to the scenario

Situation: The site has a "Contact" or "Book a consultation" form. After submission, the scenario should run — create a ticket, send a confirmation email.

Trigger: Webhook — the external system sends an HTTP request to the platform URL. The section receives data from the request body.

Details: Configure webhook

Use case 3: Automatic reaction to ticket creation

Situation: When a new ticket is created (e.g. from the widget), the system should automatically send a greeting to the customer or assign an operator.

Trigger: Internal Events — event "Ticket created". You can add filters: only certain channels, only new customers.

Details: Configure internal events, Internal events reference

Use case 4: Escalation when SLA is breached

Situation: If a ticket stays in "Open" status too long or the SLA deadline is approaching — run an escalation scenario (e.g. notify the supervisor).

Trigger: Internal Events — events "Time in status exceeded" or "SLA deadline approaching". Configure status, wait time, channels.

Details: Configure internal events, Internal events reference

Use case 5: Reaction to message delivery error

Situation: A message was not delivered to the customer (e.g. user blocked the bot in Viber). The system should send an email to the supervisor or switch the communication channel.

Trigger: Internal Events — event "Message delivery error". You can filter by channel and error code.

Details: Configure internal events, Internal events reference

Use case 6: AI assistant calls scenario logic

Situation: The AI assistant (Cursor, Fastline) needs to get exchange rates, check product availability, or run other logic already implemented in the scenario.

Trigger: MCP Tool — the section is exposed as a tool for the AI. The AI passes parameters (e.g. currency, date) and receives the result.

Details: Configure MCP Tool, Connect AI assistant via MCP

Use case 7: Testing and manual run

Situation: You need to test the scenario without external events — click "Run" in the editor. Or the section is invoked on a schedule (cron).

Trigger: Process start — no external trigger. No additional configuration.

Details: Configure process start

Quick trigger selection

If you need…Choose trigger
Run on message in messenger or widgetChannels
Run on HTTP request from CRM, form, APIWebhook
Run on system event (ticket, SLA, error)Internal Events
Run from AI assistant (Cursor, Fastline)MCP Tool
Manual run or testProcess start