# ZazzyAgent Flow Builder | Complete Guide to WhatsApp Automation Flow Builder is the visual automation system inside ZazzyAgent. It lets you create structured customer journeys without having to write traditional application code. You can build conversations using: * Text * Images * Videos * Audio * Files * Buttons * Interactive messages * Lists * Templates * Conditions * User Input * AI replies * HTTP APIs * Google Sheets data * Labels * Sequences * WhatsApp Flows * Other supported actions ## What is a flow? A flow is a series of steps that defines what happens during a customer conversation. A simple flow could be: **Customer says hello** ↓ **Welcome message** ↓ **Choose an option** ↓ **Customer selects "Products"** ↓ **Show product choices** ↓ **Customer selects a product** ↓ **Show product information** A more advanced flow might include an API, customer information, conditions and human handoff. ## When should I use Flow Builder? Flow Builder is useful when you know the steps a customer should follow. Examples: * Lead capture * Product selection * Appointment requests * FAQs * Customer support * Qualification * Order-related workflows * Data collection * Menu systems Use AI when the conversation needs natural-language understanding. Use Flow Builder when you want a predictable, structured process. You can also combine both. ## Create a flow Open the Flow Builder section in ZazzyAgent and create a new flow. Give it a useful name. Examples: > Main WhatsApp Menu > Lead Qualification > Product Finder > Appointment Booking > Customer Support Avoid generic names such as: > Flow 1 > Test Flow Clear names become much more useful as your account grows. ## Start with the conversation goal Before adding nodes, decide what the flow is supposed to accomplish. Example: > Collect enough information from a new lead to determine which sales representative should handle the customer. That gives you a clear destination. ## Add a message A text message is the simplest flow element. Example: > Hi! Welcome to our store. What can we help you with today? Keep messages short and easy to understand. ## Add buttons Buttons let customers choose from predefined options. Example: > What would you like to do? **View Products** **Track Order** **Talk to Support** Buttons are particularly useful when the number of possible choices is limited. ## Add interactive lists Lists are useful when you have more choices than can comfortably fit into buttons. Example: > Select a product category: * Men's clothing * Women's clothing * Accessories * Footwear ## Add media Flows can contain supported media such as: * Images * Videos * Audio * Files Use media when it improves the conversation. Don't add images simply because the feature exists. ## Add conditions Conditions allow the flow to behave differently depending on customer information. Example: > If Customer Type = VIP → Send VIP support message Otherwise: → Send standard support message Conditions can use available subscriber information and custom fields depending on the configuration. ## Add User Input User Input lets you collect information from customers. Example: > What is your name? Then: > Which product are you interested in? Then: > What is your budget? The collected information can be stored and reused later in supported workflows. ## Use custom fields Custom fields let you save structured customer information. Example: **Product Interest = Shoes** **Budget = ₹5,000** **City = Mumbai** You can then use that information in later automation. ## Use AI in a flow AI can be useful when customers aren't following a predictable button-based path. For example, a flow might ask: > What can we help you with? Instead of forcing the customer to choose a button, an AI Agent can understand: > I need a black shirt for a wedding under ₹2,000. The flow can then continue using AI or move to a structured path. ## Connect an HTTP API The HTTP API element allows a flow to communicate with an external system. Examples: * Retrieve product information * Check availability * Retrieve customer information * Query an external CRM * Get pricing * Retrieve an external record The exact request and response depend on the API you're connecting. ## Use Google Sheets data Supported Google Sheets functionality can allow a flow to work with spreadsheet data. Examples: * Product lists * Lead information * Lookup tables * Collected responses ## Add a sequence A customer can be subscribed to a sequence from a workflow when appropriate. Example: Customer completes a lead form. ↓ Save their details. ↓ Add "New Lead" label. ↓ Subscribe them to a sales follow-up sequence. ## Add a label Labels are useful for marking customers based on what happened during the conversation. Example: > Customer asked for pricing → Add **Pricing Interested** ## Add a WhatsApp Flow WhatsApp Flows can be used when you need a structured form experience inside WhatsApp. For example: > Name → Email → Date → Service → Submit This is useful for structured data collection. ## Connect flow steps The key to Flow Builder is the relationship between nodes. Think about every connection as: **What happened?** → **What should happen next?** Example: Customer chooses: **Track Order** ↓ Ask for order number ↓ Retrieve order ↓ Display result ## Test before publishing Always test the complete journey. Don't test only the first message. Test: * Every button * Every branch * Every condition * Every User Input field * Every API * Every template * Every error path ## Design for customers who don't follow instructions A flow might expect: > Select 1 for Sales or 2 for Support. A customer might instead type: > I want to return my order. Your automation needs to account for natural customer behavior. This is one reason combining structured flows with AI can be powerful. ## Keep large flows manageable As a flow grows, divide complicated processes into logical sections. For example: **Main Menu** → Sales Flow → Support Flow → Order Flow → Appointment Flow Avoid creating one enormous conversation tree containing every feature of your business. ## Flow Builder vs AI Agent Use **Flow Builder** when: * The process is predictable. * You need buttons. * You need structured forms. * You need precise branching. * The customer must follow specific steps. Use **AI Agent** when: * Customers ask questions naturally. * The conversation changes direction frequently. * You need natural-language understanding. * Different questions need different responses. Use both when appropriate. ## Flow troubleshooting When a flow isn't working, check: 1. Is the flow published? 2. Is the trigger working? 3. Does the previous node connect to the next node? 4. Is the condition evaluating correctly? 5. Are required variables populated? 6. Are custom fields available? 7. Is the API returning the expected data? 8. Is the selected WhatsApp template approved? 9. Is the customer inside the appropriate messaging window? A flow should be built around the customer's journey, not around the number of features you can fit into it. [zazzyagent.com](http://zazzyagent.com)