Moving between sections: entry and exit
Scenarios are split into sections. The Start node defines how a section is triggered from outside (channels, webhook, events). To go from one section to another inside the bot, use:
- Exit point — in the source section: «go to another section».
- Entry point — in the target section: «land here when jumping from elsewhere».
An Entry point can also accept HTTP / deep links when the type is webhook — then the entry is external, not from an Exit node.
Start node vs Entry point
| Start node | Entry point | |
|---|---|---|
| Per section | Exactly one | Can be several |
| Role | How the section starts from outside | Where a cross-section jump or external call lands |
| Settings | Channels, webhook, events, MCP, … | entry (from Exit) or webhook |
More: What is the Start node.
Wiring Exit → Entry
- In the target section, add an Entry point and set connectorAlias (unique link id).
- In the source section, add an Exit point and pick target section — the builder links them.
- Context (channel, chat) is preserved — the conversation continues.
Parameters: Entry point, Exit point.
Cross-process jumps depend on product capabilities; see crossProcess in the Exit point reference.
Quick checklist
- Open the target section → Entry point (type entry) → connectorAlias.
- In the source section → Exit point → targetSection.
- Draw edges on the canvas after Exit and after Entry.
- For webhook entry, configure URLs per Entry point.