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

# WhatsApp Flows explained: screens, states and rules

> What WhatsApp Flows are, static and endpoint Flows, the states a Flow moves through, what Meta requires before you publish, and how Flowella builds them.

A WhatsApp Flow is a form or short app that opens inside a WhatsApp chat. The customer taps a button, a screen slides up with questions, dropdowns, date pickers or consent boxes, and their answers come back to you when they submit. Flows are defined in **Flow JSON**, published to Meta, and sent from a template button or an interactive message.

> [!NOTE]
>
> **In Flowella.** Supported. Flowella builds Flows from your HubSpot forms, or from scratch in the [Flow designer](https://knowledge.flowella.io/app/flow-designer.md), and publishes them for you, so you never write Flow JSON. Flowella sends Flows from a template's Flow button, and records every submission. See [Flows](https://knowledge.flowella.io/app/flows.md).

## The building blocks

| Term | What it means |
| - | - |
| **Flow** | One task the customer completes, such as "Book a visit" or "Request a quote" |
| **Screen** | One page of the Flow, with its own components and a button at the bottom |
| **Component** | One element on a screen: text, an input, a list, a date picker, an opt-in, an image |
| **Flow JSON** | The definition of the screens and components, with a version number. See [Flow JSON versions](https://knowledge.flowella.io/whatsapp/flows/flow-json-versions.md). |
| **Endpoint** | An optional server that the Flow calls to load data or check answers while the customer fills it in |
| **Flow token** | An identifier the business sets when it sends the Flow, returned with the answers so they can be matched to the right person |

## Static and endpoint Flows

| | Static Flow | Endpoint Flow |
| - | - | - |
| How it works | Everything is in the Flow JSON. Answers arrive when the customer finishes. | The Flow calls your server while it runs, for example to check answers or load options. |
| Health monitoring | None | Meta monitors the server and can throttle or block the Flow. See [Flow health](https://knowledge.flowella.io/whatsapp/flows/flow-health.md). |
| Setup | None beyond publishing | An encryption key on the phone number and a server that answers health checks. See [Flow endpoints and security](https://knowledge.flowella.io/whatsapp/flows/flow-endpoints-and-security.md). |

> [!NOTE]
>
> **In Flowella.** Flows built from HubSpot forms are endpoint Flows: Flowella hosts the endpoint, which checks each submission against the live HubSpot form before the customer sees the thank-you screen. Flows from the Flow designer and the Flowella API are static.

## What Meta requires

Anyone can build a Flow, but to publish and send one Meta requires:

* A [verified business](https://knowledge.flowella.io/whatsapp/accounts/business-verification.md).
* A registered phone number on the WhatsApp Business Account.
* A good messaging quality rating. See [Quality rating](https://knowledge.flowella.io/whatsapp/limits/quality-score.md).
* Valid Flow JSON on a version that isn't frozen or expired.
* For endpoint Flows, a signed encryption key on the number and a healthy endpoint.

In Flowella, a missing requirement shows as a badge such as **Verification required** or **Registration required** when you sync. See [Sync errors](https://knowledge.flowella.io/app/flows.md#sync-errors).

## The states a Flow moves through

| State | Set by | What it means |
| - | - | - |
| **Draft** | You | Being built. Can only be sent for testing, and shows a draft banner. The only state in which a Flow can be deleted. |
| **Published** | You | Live. Can be sent to anyone. |
| **Throttled** | WhatsApp | The endpoint or screen navigation is unhealthy. Customers can still open it, but you can send it only 10 times an hour. |
| **Blocked** | WhatsApp | Health got worse. You can't send it, and customers can't open Flows they already received. |
| **Deprecated** | You | Retired for good. It can't be sent, but customers who already have it may still submit it. |

Throttled and Blocked are only for endpoint Flows. WhatsApp moves a Flow back to Throttled, then Published, once health recovers.

> [!NOTE]
>
> **In Flowella.** A sync publishes straight away, with no draft step. Flowella refuses to send a template whose Flow is deprecated. For Flows you manage through the Flowella API, `GET /v1/flows/{id}` refreshes the state from Meta and the `flow.status_updated` webhook reports changes. See [Webhooks](https://knowledge.flowella.io/api-reference/webhooks.md).

## How a Flow reaches the customer

| Route | When you can use it |
| - | - |
| **Template with a Flow button** | Any time, once the template is approved. This is how you start a conversation with a Flow. |
| **Interactive Flow message** | Only while the customer's [24-hour window](https://knowledge.flowella.io/whatsapp/messaging/customer-service-window.md) is open |

See [Sending Flows](https://knowledge.flowella.io/whatsapp/flows/sending-flows.md).

## Where Flows work

Flows open on Android 6.0 and later and iOS 12 and later. Meta added WhatsApp Web and Desktop from December 2025. See [Flow client support](https://knowledge.flowella.io/whatsapp/flows/flows-client-support.md).

## Related

> [card] [Flows in Flowella](https://knowledge.flowella.io/app/flows.md)
>
> Turn a HubSpot form into a Flow.

> [card] [Flow designer](https://knowledge.flowella.io/app/flow-designer.md)
>
> Build a Flow without HubSpot.

> [card] [Flow components and limits](https://knowledge.flowella.io/whatsapp/flows/flow-components-and-limits.md)
>
> What a screen can hold.

> [card] [Flows error codes](https://knowledge.flowella.io/whatsapp/errors/flows-error-codes.md)
>
> Publishing and sending errors.

Checked against Meta's documentation on 18 November 2026: [WhatsApp Flows overview](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides), [Lifecycle of a Flow](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides/lifecycle) and [Sending a Flow](https://developers.facebook.com/documentation/business-messaging/whatsapp/flows/guides/sendingaflow).


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