Home Getting to Know Controlled Flows
📖

Getting to Know Controlled Flows

Winderlly Fabrício Rissetto Ian Kraskoff
By Winderlly and 3 others
• 5 articles

How the ClaudIA and Controlled Flow Interaction Works

Interaction: Customer <-> ClaudIA <-> Controlled Flow Detailed Flow Explanation Customer sends a message: The customer initiates contact by sending a message to ClaudIA. The message can be a simple question, an inquiry about an order status, or a more specific question that requires an automated flow. ClaudIA interprets the message Upon receiving the message, ClaudIA, powered by a GPT-based model, begins processing the content. The model conducts a deep linguistic analysis to understand the customer's intent, the message context, and to identify important entities. ClaudIA checks the type of content With the message processed, ClaudIA determines what type of response is necessary: - Content N1: if the message is simple and straightforward, ClaudIA responds automatically with an answer from the knowledge base. - Content N2: if the question is more complex or requires human assistance, ClaudIA transfers the conversation to the N2 team. - Interactive Content: if the inquiry involves a more complex request (e.g., checking order status, API-based information retrieval, or Google Sheets integration), ClaudIA activates the Controlled Flow. Controlled Flow (Interactive Content) When the content is interactive, ClaudIA triggers the Controlled Flow. This flow can include: - Queries (API, Google Sheets, LLM prompt, tree flows, JavaScript, etc.): The Controlled Flow performs the defined queries, such as checking order status or retrieving specific data. - Response Generation: The response generated by the Controlled Flow is then sent to the customer. Flow Completion After the Controlled Flow execution, the interaction can proceed in different ways: - Return to ClaudIA: if configured, the flow returns to ClaudIA, which continues the interaction. "End Flow [N1]". - Escalated to N2: if set up, the conversation is escalated to the N2 team for more in-depth support "Forward to Human [N2]".

Last updated on Aug 29, 2026

Step-by-step Guide to Launching a New Controlled Flow

[Step 1] Understanding which flow will be built The first step in launching a new Controlled Flow is to define its purpose. Will it be a Controlled Flow that communicates the status of the customer's order? Will it verify the customer's plan? Will it delete the user's account? To do this, understand the questions users will ask that should trigger the new Controlled Flow, as in the examples below of user/Controlled Flow questions: - "Where is my order?" → Order Status Controlled Flow - "I forgot my password" → Password reset Controlled Flow - "My account is locked" → Account unlocking Controlled Flow - Validating some information at the beginning of the interaction → Initial validation Controlled Flow [Step 2] Drawing the flow sketch We recommend using Miro or any digital "White Board" tool to sketch each step (a simplified flowchart). You need to understand: - The question the customer will ask that triggers this Controlled Flow For example: "Where is my order?" - The variables that need to be mapped For example: customer's Order ID field - The data sources that the Controlled Flow will use For example: Google Sheets or API - The responses to be provided to the customer based on the mapped variables and backend queries For example: "Your order status is {{orderStatus}}" [Step 3] Setting up the flow in Controlled Flow This guide provides step-by-step instructions for setting up a flow in Controlled Flow. Follow these steps: Step 1: Request the creation of a workspace in Controlled Flow for you (it is not created by default). Step 2: Inside the workspace, click "Create a typebot" for each new Controlled Flow, then select "Start from scratch" to create a Controlled Flow. Step 3: Begin constructing a new Controlled Flow. For more detailed instructions on building a complete Controlled Flow: How to create a flow in Controlled Flow via API or How to create a flow in Controlled Flow using Google Sheets [Step 4] Setting up in ClaudIA (linking the created flow to an INTERACTIVE section) This guide explains how to ensure that Controlled Flow will be activated by ClaudIA. Step 1: Do not use generic texts in the "response" of the updated/created section. It is essential that this response is unique to optimize the Controlled Flow's trigger. Example of an appropriate section (with a specific "response" for the case): Example of an inappropriate (generic) section: Step 2: Ensure that the section's Type is marked as "INTERACTIVE". This option is only available after Setting up in Controlled Flow. Step 3: Select the Flow ID of the Controlled Flow you want to trigger when this section is used. Done! Your interactive section is fully configured. You can test the integrated behavior between ClaudIA <> Controlled Flow directly in the panel's Playground. [Step 5] Reviewing the Controlled Flow's termination strategy End Flow [N1] When this card is used, the ticket will not be closed at the end of the Controlled Flow's interaction, and the customer will return to interact with ClaudIA. Ideal for Controlled Flows activated through a ClaudIA section. Answer Ticket [N1] When used, this card prevents the ticket from closing at the end of the Controlled Flow's interaction, allowing the customer to resume interaction with ClaudIA. If the interaction is initiated by the Controlled Flow, ClaudIA will respond to the user's first message, making it ideal when the Controlled Flow starts the interaction. Note that a Bubble Text card with some content must precede the Answer Ticket; without it, functionality may be compromised, resulting in Controlled Flow errors. Close Ticket [N1] When this card is used, the ticket will be closed at N1. If the customer sends a new message, a new ticket will be created. Forward to Human [N2]: When this card is used, the ticket will be closed by ClaudIA and transferred to a customer agent (escalated to N2). Important precautions 1. Fill in the "Topic" field only if ClaudIA has sections with different topics (multi-prompt). 2. Always include a text Bubble before the Forward to Human [N2] card when used. [Final Step] Testing the created Controlled Flow Testing a new Controlled Flow Before deploying a new flow and replacing a critical section, it is essential to test the Controlled Flow to identify improvement opportunities. We recommend testing in three different ways: 1. Through the Controlled Flow's own workspace 2. Through ClaudIA Panel's Playground 3. Through the official channel 1. Testing in the Controlled Flow's workspace Tests can be performed using the "Test" button in the top right corner of the page. While it has some limitations, such as not considering all integrations with ClaudIA (e.g., variable helpdeskId), it is a quick way to perform multiple tests in a short period. 2. Testing in ClaudIA Panel's Playground To test a Controlled Flow via ClaudIA panel's Playground, create a content section in ClaudIA that triggers the Controlled Flow. Create a section with a title unlikely to be used by ClaudIA for responding to a user, for example, "Test Controlled Flow - how do I make a polyjuice potion with a mixer?". With this section, send the section's title message (Test Controlled Flow - how do I make a polyjuice potion with a mixer?) in the playground. 3. Testing via the official channel Similar to testing via Playground, to test through official channels like WhatsApp, email, or widget, create a content section in ClaudIA. Follow the same steps as in Playground, but send the message through the chosen official channel. This option is useful for testing flows that perform validation based on helpdeskId.

Last updated on Aug 26, 2026

Basic Guide on How to Use Controlled Flow's Features and Buttons

Welcome to the ultimate guide on building flows with Controlled Flow, the visual builder of Cloud Chat. Here you'll understand what each button does, when to use and how to set it up — with practical examples that help you decide the best path for your case. 🧱 How does a flow work? A flow is like a guided conversation, with a beginning, middle, and end. - It can start with a message (e.g., “Hello! How can I assist you?”) - The customer responds (e.g., “I want to check my order status”) - Controlled Flow understands and decides what to do with that information - And proceeds: fetching data, routing, or ending the conversation 💡 Each step is a block, and you can connect blocks like assembling a puzzle. 🔢 Types of available blocks 💬 Bubbles (Messages) 📌 Text - What is it? Block used to send visible messages to the customer (or internal user). - What does it do: Sends a message to the customer. - When to use: Whenever you want to display information, confirmation, notification, or instruction. - How to use: Drag the block into the flow, write your message in the “Text” field, and that's it. - Example: “Hello! Please fill out the following form to proceed with your request.” ✏️ Inputs (Data Collection) 📌 Text - What is it? Collects data entered by the user: name, code, order number, etc. - When to use: To get the order number, CPF, email, or any other data. - How to use: Place the block in the flow, write the question, and define the variable that will store the answer (e.g., customer_name). Example: - “What is your order number?” - Store as: order_number Logic This is where the flow’s “decisions” start — like a “if this, then that”. 🔁 Set Variable - What is it? Creates or updates a variable — a “box” where you store a value to reuse later in the flow. - Why is it useful? - Reusability: Define once and use in multiple places. - Organization: Keeps the flow cleaner and more readable. - Automation: Can store the result of calculations, integrations, or inputs. - Decision making: Can be used in conditions to choose different paths. - How to use? 1. Drag the “Set Variable” block into the flow. 2. Choose an existing variable or create a new one (e.g., user_type). 3. Assign a value: - Manually (e.g., "customer") - From another point in the flow (e.g., API response or input) - Examples: - flow_status = "waiting_for_validation" - discount = 0.15 - final_message = customer_name + ", your request has been received!" 🔍 Condition - What is it? Checks a logical condition (e.g., if status == "approved") and guides flow based on the answer. In other words, creates branches: If the value X is Y, follow this path; otherwise, follow another. - How to use? 1. Drag the “Condition” block 2. Choose the variable to test 3. Define the value to compare (e.g., status == "approved") 4. Configure what happens for “Yes” and “No” - Example: If customer_type == "vip" → show a personalized message Otherwise → continue with the standard flow 💻 Script - What is it? - Block for users who can do some programming (JavaScript). - Allows running JavaScript code within the flow — useful for calculations, formatting, advanced logic, etc. - Can be used to calculate deadlines, format numbers, or other technical tasks. - How to use? - Drag the “Script” block - Enter your JS code - Define input and output variables - Example: Calculate days between two dates, or format a CPF with dots. Shortcuts and Organization 🔄 Jump - What is it? - Makes the flow “jump” to another part without passing through intermediate blocks. - Useful to reuse parts or shorten paths. - When to use? - To reuse parts of the flow - To redirect in a “loop” - To skip unnecessary steps based on a condition - Example: If user_type == "internal", jump directly to the “End” block 🔁 Typebot - What is it? - Allows embedding another flow within the current flow. - Permits nesting one flow inside another. - When to use? - To reuse a generic flow (e.g., data verification) - To modularize the flow and ease maintenance - Example: - You can create a small flow for “CPF validation” and use it in various flows. 🔗 5. Integrations (connecting with other systems) 🧠 ClaudIA - What is it? Integrates with Cloud Humans' AI for automation and intelligent responses. Connects with ClaudIA to: - Transfer conversation to N1 or N2 - End the conversation - Change the topic or context of the interaction - How to use? Drag the button into the flow, define the desired interaction with ClaudIA (e.g., transfer to N2, transfer back to ClaudIA / N1, set a topic, etc.). 🌐 HTTP Request - What is it? Allows Controlled Flow to connect with external APIs (GET, POST, etc.) - How to use? - Drag into the flow, configure the method (GET, POST, etc.), URL, and required parameters. - Set up the method, URL, headers, and request body - Use variables to send and receive data - Example: Check order status in your ERP Get the status of an order in another software 📊 Google Sheets - What is it? Integrates with Google Sheets to read or write data in spreadsheets. - How to use? Drag the button, connect your Google account, choose the spreadsheet, and set the operation (read or write data). - Example: - Check if the user's CPF is on a list - Save the data entered during the interaction 🤖 OpenAI / Anthropic - What is it? - Allows sending prompts to LLM models like GPT or Claude and using the response in the flow. - Enables using advanced AI models to generate responses or process data. - How to use? Drag, connect to the desired AI service, and set prompts and parameters. - Example: Summarize a technical explanation Generate natural language responses Validate if the customer wrote option 1, 2, or 3 in cases where they often choose the wrong option 📅 Cal.com - What is it? - Allows scheduling meetings directly within the flow - Integrates with Cal.com to manage and schedule meetings automatically. - How to use? Drag the button, connect your Cal.com account, and set up scheduling options. - Connect your Cal.com account - Choose the meeting type and available times 📤 Email - What is it? - Sends automatic emails within the flow, directly from Controlled Flow - Sends emails to the customer or team. - How to use? Drag, set recipient, subject, and email content. - Example: Send a summary of the conversation or a contract link ⚙️ Make / Zapier - What is it? - Connects Controlled Flow with external platforms using pre-made automations - These external automation platforms further expand Controlled Flow's possibilities. - How to use? Drag into the flow, connect to your chosen platform account, and define the automations and flows. - Example: - Trigger an automation in your CRM - Update a leads database 🛠️ How to build your first flow from scratch Example: “I want to check my order status” 1. Initial message (Text) “Hello! I can help you check your order status.” 2. Question (Input) “What is your order number?” → Store this as order_number 3. Condition (Condition) If the number is filled, proceed to the next step. 4. Integration (HTTP Request) Query your API or spreadsheet with the provided number. 5. Final message (Text) “The status of your order is: {{order_status}}.” 🧠 Tips for Beginners - Use clear names for variables. Example: customer_name, plan_type, email_response - Think like a script: what would you say if talking to the customer? - Test in the Playground whenever you finish a section. - Start simple: you can improve gradually. - If in doubt, ask: “What do I want to happen after this?” Now you know everything about how to make the most of each button and feature of Controlled Flow! 🚀✨

Last updated on Jun 24, 2026

Collaborative Editing in Controlled Flow

🔄 How does collaborative editing work in Controlled Flow? Controlled Flow uses a queue system to organize multiple users in the same flow. - Only one user at a time can edit (Editor mode) - Others remain in Read-Only mode, following in real-time. When the editor leaves or is removed due to inactivity, the next person in the queue takes over editing automatically. 👥 Who can edit a flow? The order is determined by arrival: 1. The first user who opens the flow becomes the Editor 2. Others automatically join the waiting queue 3. When the current editor leaves, the next in line gains editing control 🖥️ What are the access modes? - Edit Mode → you can drag blocks, change settings, and publish changes normally - Read-Only Mode → you can view the entire flow and even test it, but cannot edit 🔎 How do I know which mode I am in? The interface displays clear indicators: - Edit Mode → a sidebar appears with available blocks and the Publish: button: - - Read-Only Mode → a "READ-ONLY" warning appears at the top: - - The connected users icon (👥) shows how many people are accessing the flow; hovering over it reveals: - The highlighted (bold) Editor - Other users in view-only mode - - ⏳ What happens if I become inactive? To prevent locks: - Controlled Flow monitors your activity - If you remain ~10 minutes inactive, you lose editing rights - The next user in line takes over as Editor 🔄 How do I pass the turn to another user? If you want to release editing rights: 1. Save your changes 2. Exit the flow 3. The next user in line automatically gains editing access 📑 Can I duplicate a flow to edit separately? Yes. If you don't want to wait in line to test a change, you can click Duplicate and create your own editable copy. 💾 Are my changes lost when someone else takes over? Only if you remain inactive after 10 minutes and haven't published your changes.

Last updated on Jun 24, 2026