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

# Flows: the Fliqr AI Flow Builder

> Build deterministic, visual conversation scripts with the Fliqr AI Flow Builder — concepts, blocks, publishing, limits, and best practices.

Flows are visual conversation scripts. You design every path on a canvas: messages, questions, branches, delays, API calls, and handoffs. When the conversation shape is known in advance — menus, qualification, booking, onboarding — use a Flow.

## Flow vs AI Agent

|                  | Flow                                             | AI Agent                              |
| ---------------- | ------------------------------------------------ | ------------------------------------- |
| Logic            | Your explicit script                             | LLM reasoning                         |
| Unexpected input | Falls through to Default Reply or a catch branch | Model improvises                      |
| Output           | Exactly what you design                          | Natural language (or structured JSON) |
| Token cost       | None for scripted steps                          | Charged per model call                |

Use a Flow when you know the paths. Use an [AI Agent](/docs/core-concepts/ai-agents) when contacts can ask anything. Mix them with the **AI Action** block when you need one LLM decision inside a scripted path.

## How Flows fit the product

1. **Build** the script in Flow Builder
2. **Publish** so other tools can use it
3. **Trigger** it from [Automation Rules](/docs/core-concepts/automation-rules), a broadcast, the inbox, a menu, or the API
4. **Store data** on [Contacts](/docs/core-concepts/contacts) with tags and custom fields as the Flow runs

## Start here

<CardGroup cols={2}>
  <Card title="Concepts" icon="lightbulb" href="/docs/core-concepts/flows/concepts">
    Deterministic paths, personalization, drafts vs published, omnichannel.
  </Card>

  <Card title="Builder" icon="diagram-project" href="/docs/core-concepts/flows/builder">
    Canvas tour and how blocks connect.
  </Card>

  <Card title="Build" icon="screwdriver-wrench" href="/docs/core-concepts/flows/messages-and-media">
    Messages, data capture, conditions, delays, APIs, dynamic content, and JSON extract.
  </Card>

  <Card title="Operate" icon="play" href="/docs/core-concepts/flows/test-and-publish">
    Test, publish, drip campaigns, triggers, and duplicates.
  </Card>

  <Card title="System fields" icon="brackets-curly" href="/docs/core-concepts/flows/system-fields">
    Built-in {{placeholders}} for contacts, ads, commerce, and more.
  </Card>

  <Card title="Common errors" icon="triangle-exclamation" href="/docs/core-concepts/flows/common-errors">
    Fix empty messages, messaging windows, templates, and API failures.
  </Card>
</CardGroup>

## Quick start

<Steps>
  <Step title="Open Flow Builder">
    Go to **Flows → Create New Flow** and name it by purpose (for example, `Lead qualification — WhatsApp`).
  </Step>

  <Step title="Add blocks">
    Start with a **Message**, then add **Quick Replies** or **User Input**. Connect outputs with arrows.
  </Step>

  <Step title="Personalize">
    Use `{{first_name}}` and your custom fields in message text. See [Collect data](/docs/core-concepts/flows/collect-data).
  </Step>

  <Step title="Test and publish">
    Click **Test Flow**, walk each branch, then **Publish**. See [Test and publish](/docs/core-concepts/flows/test-and-publish).
  </Step>

  <Step title="Attach a trigger">
    Point an [Automation Rule](/docs/core-concepts/automation-rules) (keyword, new contact, button) at the published Flow — or send it from the inbox / API.
  </Step>
</Steps>

<Warning>
  Publishing replaces the live version for contacts already mid-conversation. For breaking changes, [duplicate the Flow](/docs/core-concepts/flows/manage-and-duplicate) and route new contacts to the copy.
</Warning>

## Related

<CardGroup cols={2}>
  <Card title="Automation Rules" icon="bolt" href="/docs/core-concepts/automation-rules">
    Decide when a Flow starts.
  </Card>

  <Card title="Contacts" icon="address-book" href="/docs/core-concepts/contacts">
    Tags, custom fields, and segments Flows read and write.
  </Card>

  <Card title="Limits" icon="gauge" href="/docs/core-concepts/flows/limits">
    Blocks per flow, media sizes, and condition caps.
  </Card>

  <Card title="Recipes" icon="book" href="/docs/core-concepts/flows/recipes">
    Proven patterns for menus, qualification, and booking.
  </Card>
</CardGroup>