> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatflows.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation flow builder

> Build an automation step by step: choose what starts it (a message, a keyword or a Shopify event), then add messages, questions and actions.

The **Flow Builder** is where you create your chatbot conversation. Choose from different flow steps such as [**Text Message**](https://docs.chatflows.io/automation/flow-steps/basic.md#text-message), [**Button Message**](https://docs.chatflows.io/automation/flow-steps/basic.md#button-message), [**Ask Question**](https://docs.chatflows.io/automation/flow-steps/ask.md#ask-question), [**Condition**](https://docs.chatflows.io/automation/flow-steps/advanced.md#condition), or [**API Request**](https://docs.chatflows.io/automation/flow-steps/advanced.md#api-request) then connect them to control what happens next. Every flow begins with a [**Start Trigger**](#the-start-trigger), which determines when the conversation starts. After that, each flow step runs in the order you've connected them.

Think of it like drawing a conversation on paper:

When someone says **"hi" → send them a welcome message. Then → show three buttons → If they tap "Book a table"**, ask for their preferred date.

## How the builder works

**1. Open the builder**

Go to **Automations** in the sidebar, click the menu icon at the end of a flow's row, and click **Flow Builder**.

**2. Set the Start Trigger**

Every flow starts with a [**Start Trigger**](#the-start-trigger). Click it to choose who can start the flow and what should start it. For example, you can trigger the flow when someone sends a keyword or when an event occurs in your [Shopify](#shopify) store.

**3. Add flow steps**

Pick a category tab at the top — **Basic**, **Interactive**, **Ask**, **Advanced** or **Integrations** — then click a tile, or drag it into the builder.

**4. Join them up**

Connect each flow step in the order you want the conversation to happen. The chatbot follows these connections from one step to the next.

**5. Fill in each flow step**

Click a flow step card to open its settings on the right. Then fill in the details required for that step, such as the message, buttons, questions, or other options.

**6. Save**

Click **Save Flow** at the top right. If any required fields are missing, the affected flow steps are highlighted in red, and the Save button stays disabled until you fix it.

> [!TIP]
>
> Type **@** in almost any text box to drop in a merge field, such as the contact's first name. See [Merge Fields](https://docs.chatflows.io/messaging/merge-fields.md).

## The Start Trigger

Every flow begins here. The Start Trigger decides when your chatbot starts. Open the **Start Trigger** settings, then choose one of the two Trigger Sources.

* **Message** — someone sends you a WhatsApp or Messenger message.
* **Shopify** — something happens to an order in your Shopify store.

The rest of the card changes depending on which one you choose. The following sections explain each option.

### Message

The most common choice. The flow starts when someone messages you.

![Start Trigger settings with Trigger Source set to Message, Contact Type showing Lead and Customer selected, Trigger Type set to On exact match, and a Keywords box containing the keyword menu](https://mintcdn.com/chatflows-docs/8QSpoWsCTFEf5plZ/automation/img/message-trigger.png?fit=max\&auto=format\&n=8QSpoWsCTFEf5plZ\&q=85\&s=d626a567a9537b394486c9dd9a453f91)

**Contact Type** — Choose which contacts can start this flow. You can select one or more contact types, such as **Lead**, **Customer**, or **Guest**.

**Trigger Type** — Choose how an incoming message is matched. There are four options:

| Option | What it means |
| - | - |
| **On exact match** | The customer's message must exactly match one of your keywords. For example, if your keyword is **menu**, only **menu** will trigger the flow. Messages like "send me the menu" or "show me the menu" won't. |
| **When message contains** | The flow starts if your keyword appears anywhere in the customer's message. For example, if your keyword is **menu**, messages like **send me the menu** or **show the menu** will also trigger the flow. |
| **First message from lead/customer** | Starts the flow when a lead or customer contacts you for the first time. After that, this trigger won't run again for the same contact. |
| **No keyword matches (fallback)** | Use this as your default flow. If no other keyword triggers match, this flow runs automatically to make sure every customer receives a response. |

**Keywords** — Available only when **On exact match** or **When message contains** is selected. Enter a keyword and press Enter to add it. Add multiple keywords or common variations so customers can trigger the flow using different words.

**Example.** If you choose When Message Contains and add the keywords **book**, **table**, and **reservation**, messages like **"Can I book a table for 4?"** or **"I'd like to make a reservation"** will automatically start the booking flow.

> [!TIP]
>
> We recommend creating one **First message from lead/customer** flow to greet new **contacts** and one **No keyword matches (fallback)** flow to handle messages that don't match any keywords. This way, every customer receives a response.

### Shopify

This flow runs automatically when an order changes in your connected Shopify store. Customers don't need to send a message. ChatFlows uses the customer's phone number to find the correct contact and start the flow.

![Start Trigger settings with Trigger Source set to Shopify, the Shopify Event set to Cart abandoned, a Send after (minutes) box with its help text, and a note about the 24-hour messaging window](https://mintcdn.com/chatflows-docs/8QSpoWsCTFEf5plZ/automation/img/shopify-trigger.png?fit=max\&auto=format\&n=8QSpoWsCTFEf5plZ\&q=85\&s=38a5b73d2412d5d14c3d2e8f438f6cc2)

Pick one **Shopify Event**:

| Event | Fires when |
| - | - |
| **Cart abandoned** | Someone starts checkout and leaves without paying. Runs after the **Send after (minutes)** delay you set (one hour unless you change it), only if they still haven't ordered. |
| **Order placed** | An order is successfully placed. |
| **COD payment received** | A cash-on-delivery order is marked as paid in Shopify. It runs after payment, not before the order ships. |
| **Order partially shipped** | Part of the order has shipped. |
| **Order shipped** | The order has shipped. |
| **Order out for delivery** | The courier is delivering it today. |
| **Order delivered** | The order reached the customer. |
| **Order cancelled** | The order was cancelled. |

**Send after (minutes).** When you pick **Cart abandoned**, a **Send after (minutes)** box appears. It sets how long to wait before the flow starts. You can enter 5 to 1,440 minutes. If you leave it empty, the wait is 60 minutes. If the shopper completes the order first, nothing is sent. Under 15 minutes is usually too soon. Shopify reports a checkout as soon as the shopper reaches it, so they may still be filling in their details. See [Recover abandoned carts](https://docs.chatflows.io/shopify/cart-recovery.md).

**What it's for.** Keep customers updated throughout their order journey. Use it to recover abandoned carts, send [order updates](https://docs.chatflows.io/shopify/order-updates.md), and reduce support questions like "Where's my order?"

**Example.** Pick **Cart abandoned** and set **Send after (minutes)** to **60**. Then send a **WhatsApp template** with a link back to their checkout. For a second reminder, create another cart-abandoned automation with a longer delay. Each one checks for an order before it sends.

> [!NOTE]
>
> The **Order out for delivery** and **Order delivered** triggers work only if your shipping carrier sends tracking updates to Shopify. If you mark orders as fulfilled manually, these triggers won't run.

> [!WARNING]
>
> Shopify flows start automatically when an event occurs in your store, not when a customer sends you a message. If the customer hasn't messaged you in the last [24 hours](https://docs.chatflows.io/getting-started/concepts.md#two-whatsapp-rules-that-shape-everything), start the flow with a [**WhatsApp Template**](https://docs.chatflows.io/automation/flow-steps/basic.md#whatsapp-template). This ensures the first message is delivered successfully.

> [!NOTE]
>
> Shopify triggers need a connected store. See [Your store and the Shopify app](https://docs.chatflows.io/shopify/shopify-admin-app.md).

## The five categories

Flow steps are organized into five categories. Each page explains every flow step in that category, what it does, and when to use it.

> [card] [Basic](https://docs.chatflows.io/automation/flow-steps/basic.md)
>
> The everyday replies — plain text, buttons, links, and approved templates.

> [card] [Interactive](https://docs.chatflows.io/automation/flow-steps/interactive.md)
>
> Lists, images, videos, documents, map pins, contact cards, and emoji reactions.

> [card] [Ask](https://docs.chatflows.io/automation/flow-steps/ask.md)
>
> Ask a question and save the answer — name, phone, email, address, location, or a file.

> [card] [Advanced](https://docs.chatflows.io/automation/flow-steps/advanced.md)
>
> Waiting, branching, tagging, updating the contact, and calling other systems.

> [card] [Integrations](https://docs.chatflows.io/automation/flow-steps/integrations.md)
>
> Write a row to Google Sheets or create a Google Calendar event.

## Builder tools

The toolbar at the top right of the page has a few helpers:

* **Undo** and **Redo** — step back or forward through your changes.
* **Snap to grid** — keeps cards neatly aligned as you drag them.
* **Auto-arrange layout** — Automatically arranges the entire flow into a clean, left-to-right layout.
* **Save Flow** — saves your work. It's disabled while any card has an error.

> [!NOTE]
>
> Some flow steps are available only on the platform that supports them. If you're building a Messenger flow, WhatsApp-only steps are hidden. If you're building a WhatsApp flow, **Messenger Template** is hidden.
>
> The WhatsApp-only steps are [**List Message**](https://docs.chatflows.io/automation/flow-steps/interactive.md#list-message), [**Call To Action**](https://docs.chatflows.io/automation/flow-steps/basic.md#call-to-action), [**Contact Card**](https://docs.chatflows.io/automation/flow-steps/interactive.md#contact-card), [**Reaction**](https://docs.chatflows.io/automation/flow-steps/interactive.md#reaction), [**WhatsApp Template**](https://docs.chatflows.io/automation/flow-steps/basic.md#whatsapp-template), [**WhatsApp Flow**](https://docs.chatflows.io/automation/flow-steps/basic.md#whatsapp-flow), and [**Ask Location**](https://docs.chatflows.io/automation/flow-steps/ask.md#ask-location).

## What's next

> [card] [Flow Collection](https://docs.chatflows.io/automation/overview.md#flow-collection)
>
> Start from a ready-made flow instead of an empty builder.

> [card] [Generate with AI](https://docs.chatflows.io/automation/generate-with-ai.md)
>
> Describe your flow in plain English and get a starting point.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.