The Start node is the entry point for all conversations in your flow. Every flow must have exactly one Start node.
When a conversation begins, the Start node receives the user's first message and stores it in a variable that can be accessed in subsequent nodes. The conversation then flows to the connected node.
Entry points allow you to create multiple conversation paths based on the first message sent by the user. When a user sends their initial message, the system matches it against the defined entry points to determine which path to follow.
An entry point you have not drawn a connection from also takes the default connection, so you only need to wire the ones that lead somewhere different.
Matching on the label means a link can carry a sentence rather than an id, which reads better to whoever clicks it: ?text=I want to see a demo and ?text=demo both arrive at the same entry point.
https://m.me/yourpage?ref=summer_sale → Pre-fills "SUMMERSALE" → Matches "summersale" entry pointhttps://wa.me/1234567890?text=support → Pre-fills "support" → Matches "support" entry pointThere is no link to pre-fill a message, so the widget offers your entry points instead: a card shows them as the way in, a chat as replies to its greeting. Picking one sends it as the first message, which is the same thing a campaign link does. The conversation is only created once someone picks, so a page carrying the widget costs nothing until a visitor says why they came.
Entry Points
options
Define multiple entry points for your flow.
Each option creates a separate output handle on the node. The flow continues through the handle corresponding to the selected/matched option.
Requirements:
This node stores its output in a variable that can be referenced in subsequent nodes using the {{variable}} syntax.
{{variable}}
string
The first message sent by the user to start the conversation