Skip to content

Conversation Flows

The Conversation Flows page lets tenant administrators author data-driven flows that the chatbot runs when a contact picks a Flow node from a Conversation Menu. A flow is a sequence of typed variables and ordered steps; each step can prompt the contact for input, invoke a Conversation Skill, or branch based on what the contact replied.

Conversation Flows page showing the flow list on the left and the Variables / Steps / Settings tabs on the right

  • Route: /communications/flows
  • Menu Path: Communications → Conversation Flows
  • Primary audience: Tenant administrators building self-service conversational workflows.
PermissionDescription
communications.access (Read)View flows and their steps
communications.access (Admin)Create, edit, clone and delete flows; add or reorder variables and steps
  • Left rail — the list of flows for the tenant. Each entry shows the flow name and a short description.
  • Right pane — three tabs for the selected flow: Variables, Steps and Settings.
StatusDescription
DraftThe flow is being authored and is not yet attached to any menu.

Once a flow is attached to a Flow node in a Conversation Menu it can be invoked by contacts; there is no separate “publish” step beyond saving the flow.

Each variable declares a typed slot that the flow fills from contact input or skill output, and that subsequent steps can reference.

FieldDescription
NameIdentifier used by steps (for example, customer_phone)
TypeText, number, date, boolean, BP ID or other registered types
DescriptionInternal note about how the variable is used
DefaultOptional default value used when the contact does not supply one

Variables can be reordered with drag and drop.

Steps run sequentially. Each step is one of:

Step typeDescription
PromptSends a message to the contact and waits for a reply, storing the reply in a variable.
SkillInvokes a Conversation Skill using the current variables as parameters and writes the result to a variable.
BranchPicks the next step based on a variable value.
SendSends a final message to the contact (often the formatted result of an earlier skill call).

Steps can be reordered with drag and drop.

FieldDescription
NameDisplay name of the flow
DescriptionInternal description of what the flow does
ActionDescriptionPermission
New flowOpen the create-flow dialogcommunications.access (Admin)
ActionDescription
CloneDuplicate the flow, including its variables and steps, into a new Draft flow
DeleteRemove the flow. Flow nodes that pointed to it are surfaced in the menu editor with a “Flow no longer available” badge.
Add variable / stepAppend a new variable or step to the corresponding tab
ReorderDrag and drop a variable or step to a new position
  • Cloning preserves variables and steps but always creates the copy in Draft, with "(copy)" appended to the original name.
  • A flow cannot be deleted while any Conversation Menu still has a Flow node pointing to it — remove the menu node first.
  • Variable references in step content use {{variable_name}} syntax, mirroring how email and WhatsApp templates render placeholders.
  • Skill steps fail at runtime if the target skill has been retired or the tenant has lost access to the source module. The conversation falls back to the parent menu and the failure is recorded in Conversation Logs.
  1. Open Communications → Conversation Flows.
  2. Click New flow and name it “New customer onboarding”.
  3. On the Variables tab, add a prospect_name (Text) variable and a prospect_phone (Text) variable.
  4. On the Steps tab, add a Prompt step asking for the customer’s name and store it in prospect_name, then a Skill step calling prospects.create_or_find.
  5. Open Communications → Conversation Menus, edit the default menu and add a Flow node that points to this flow.