Use flow nodes, variables, and branches

Before you begin

Create a flow in Chatbots → your chatbot → Flows. The canvas provides Message, Question, Condition, Action, RAG, Handoff, and End nodes, alongside the starting node. Click a palette item to add a node, then use Edit node to select it. Configure destinations with the labelled Connections controls or canvas handles.

Node reference

API call (coming soon) is displayed in the action selector but does not execute an API request. Use the separately configured Functions capability when you need a supported webhook tool.

Build a branching example

1. Add a Question: “Are you a new or existing customer?” Set Store in variable to customer_type, Input type to Buttons, and add New customer and Existing customer on separate lines.
2. Under Connections, set New customer to a question asking for the visitor's name. Store it as customer_name. Set Existing customer to a question asking for their reference number. The matching output handles offer the same routing.
3. Add a Message after the name question: Thanks, {{customer_name}}. Let's find the right next step. Variable names must match the earlier question exactly.
4. To branch on free text or another stored value, add Condition. Set Variable to the existing variable name and choose an operator. Choose destinations for the true and false branches in Connections; both outcomes need a destination.
5. Use Equals, Contains, Starts with, or Ends with for text checks; Is empty and Is not empty for missing answers; and Greater than or Less than for numeric values. There are also Not equals and Not contains options.
6. If a later step needs a fixed value, add Action → Set variable, then enter Variable name and Value. Values can reference another variable with {{variable_name}}.
7. Set tag variable stores a local flow variable; it does not apply a conversation or CRM tag. Save lead in Chyt maps captured name, company, job title, service interest, team size, timeframe and project goal into a lead. Put an explicit save choice before this action. Blank or skipped answers are omitted; contact verification remains separate. Test Flow previews the capture without creating a lead. No action here confirms email delivery or a booking.
8. Connect every result to another useful step, End, Handoff, or RAG. Select Save, open Test, and restart for every route.

What you should see

Button choices follow their individual connections. A condition routes to its true or false branch. Deterministic nodes return configured text without model tokens or AI-credit usage; explicit RAG fallback requires available AI credits. Several flows can remain active together. Visitors can select a named path or type /flows to choose or switch paths; activating one flow does not deactivate the others. An unknown answer to a closed Buttons question repeats the question, while Free text accepts other answers alongside optional quick replies.

Troubleshooting

• Variable is blank: collect it before using it and check spelling in Store in variable and {{...}}.
• Numeric branch is always false: ask for a numeric value; answers such as “about ten” are text.
• A button reaches the wrong question: check its named branch in Connections. Changing one destination preserves the other branches.
• An API-call action does nothing: it is marked coming soon. Configure a supported function instead.
• AI fallback fails while other steps work: check Billing → AI credits, model availability, and source readiness.

Continue learning

Build your first flow · Integrations and functions · Plans and allowances