🚀 Entry Point Node¶
Purpose¶
The Entry Point node marks the starting point of your conversation flow. It defines when and how the assistant begins talking to a customer. Every flow must have exactly one Entry Point.
Business Scenario¶
Use the Entry Point when you need to:
- Start every conversation automatically when a customer messages your WhatsApp number
- Trigger only on specific keywords — e.g., start a "sales" flow only when the customer types "pricing" or "buy"
Configuration¶
When you click the Entry Point on the canvas, the Inspector shows these settings:
Trigger Type¶
| Option | Description |
|---|---|
| Any incoming message | The flow starts whenever a customer sends any message. This is the most common setting. |
| First contact only | The flow starts only the first time a customer messages. Returning customers skip straight to the menu. |
| Specific keyword | The flow starts only when the customer types one of your specified keywords. |
Keywords (only visible when Trigger = "Specific keyword")¶
A comma-separated list of trigger words. Matching is case-insensitive.
Example: hi, hello, start, menu
Properties¶
| Property | Type | Required | Default | Description |
|---|---|---|---|---|
triggerType |
Select | Yes | any_message |
When this flow activates |
keywords |
Text | Only if trigger = keyword | — | Comma-separated trigger words |
Inputs¶
None. The Entry Point has no incoming connections — it is always the first node.
Outputs¶
| Handle | Type | Description |
|---|---|---|
| Bottom (↓) | Continue | Connects to the first node in your flow (typically a Welcome Message) |
Connection Rules¶
- ✅ Must have at least one outgoing connection
- ❌ Cannot receive incoming connections (no target handle)
- ❌ Only one Entry Point is allowed per flow — the palette hides this node once one exists
- ✅ Can connect to: Message, Menu, Question, AI Chat, Document, Image, Condition, Send Email, API Action, Human Handoff
Example Flow Diagram¶
flowchart TD
A["🚀 Entry Point<br/><em>Any incoming message</em>"] --> B["💬 Welcome Message"]
B --> C["📋 Main Menu"]
style A fill:#dcfce7,stroke:#22c55e,stroke-width:2px
style B fill:#dbeafe,stroke:#60a5fa,stroke-width:2px
style C fill:#ede9fe,stroke:#8b5cf6,stroke-width:2pxBest Practices¶
Use "Any incoming message" for most assistants — it ensures no customer is left without a response.- Always connect the Entry Point to a Welcome Message as the first step.
- Keep keywords simple — use common greetings like
hi,hello,start. - Remember that global interrupt keywords (like
menu,hi,agent) work regardless of the trigger type.
Common Mistakes¶
| Mistake | What Happens | Fix |
|---|---|---|
| No Entry Point in the flow | Validation error: "No entry point defined" | Add an Entry Point from the palette |
| Multiple Entry Points | Validation error: "Multiple entry points found" | Delete extra Entry Points — only one is allowed |
| Entry Point with no outgoing edge | Validation error: "Entry point has no outgoing connection" | Connect it to a Welcome Message or Menu |
| Keyword trigger with no keywords | Flow never activates | Enter at least one keyword |