Flows

Flows let you define guided logic for a chatbot beyond a single free-form chat turn. Each chatbot can have multiple flows with statuses such as draft, published, and archived.

Where to find flows

Open Automation in the sidebar, then the Flows tab (the default tab). Flows live inside the Automation hub alongside Calendar, Data Sources, Connectors, and Integrations when those modules are entitled.

When to use flows

Use flows for repeatable journeys: qualification questions, troubleshooting trees, scripted handoffs, or CRM actions triggered by customer messages. Keep branching readable and test after publishing.

Flow editor

Create or open a flow to use the visual builder (/dashboard/agents/{id}/flows/{flowId}):

• Trigger nodes — when the flow starts (page load, first visit, message keywords, inactivity, connector webhooks, and more).
• Message steps — send proactive messages to the visitor.
• Ask question — collect a reply and branch on the answer.
• Conditions and variables — store answers and route logic.
• Connector action — call a connected CRM or CMS operation (for example search HubSpot contacts or list WordPress posts) when the Connectors module is active.
• Calendar action — book or check availability when the Calendar module is active.
• Webhook — call an external URL with flow context.

Save drafts while editing; publish when ready for live traffic.

Connector events

With CRM connectors connected, you can add Connector event triggers that start flows when inbound webhooks fire—for example a HubSpot deal stage change. Proactive steps can deliver messages on the website widget, Meta, Telegram, or email (when the customer has an email on file).

When a customer replies to an Ask question step from a proactive flow, Chatloop resumes the flow instead of treating the message as a generic AI chat turn.

Lifecycle

Create a flow, edit in the builder, then publish when ready. Archive flows you no longer want active. Deletion is permanent—confirm before removing production flows.

Permissions

Managing flows requires settings-level access on that chatbot (typically owner or admin). Read-only team members may not see Automation unless they have calendar module access that grants Automation visibility.

Related

• Connectors module — CRM/CMS connections used by connector steps.
• Data Sources — live database or external API lookups the assistant can use in chat.
• Social and messaging integrations — channels where proactive flow messages can appear.