> ## 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.

# How to send a WhatsApp Flow: templates and messages

> The two ways to send a WhatsApp Flow, a template Flow button or an interactive message, what each needs, and how Flowella sends Flows from every channel.

You send a WhatsApp Flow by attaching it to a message. To start a conversation, attach it to a template as a **Flow button**, which you can send any time once the template is approved. While the customer's 24-hour window is open, you can also send it in an **interactive Flow message** without a template. Either way, the customer taps the button and the Flow opens.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella sends Flows through a template with a Flow button, from the inbox, bulk send, HubSpot workflows and the API. It doesn't send interactive Flow messages without a template. When you send from the inbox, bulk send or HubSpot, Flowella sets the Flow token for you, so each submission is matched to the right contact.

## The two routes

| | Template with a Flow button | Interactive Flow message |
| - | - | - |
| When | Any time, including first contact | Only inside the customer's [24-hour window](https://knowledge.flowella.io/whatsapp/messaging/customer-service-window.md) |
| Approval | The template must be approved | None |
| Price | The template's category price | The service message price. See [WhatsApp pricing](https://knowledge.flowella.io/whatsapp/pricing/whatsapp-pricing.md). |
| Counts towards messaging limits | Yes, outside the window | No |
| In Flowella | Supported | Not available |

## A template with a Flow button

* The Flow must be published before the template is approved and sent.
* Flowella's editor allows one Flow button per template. Since April 2025, Meta lets a Flow button sit alongside other buttons, such as quick replies or a URL button.
* The template's category follows its content, like any template. A Flow that books a service someone requested can be utility, and a Flow that collects leads for an offer is marketing. See [Template categories](https://knowledge.flowella.io/whatsapp/templates/template-categories.md).
* At send, you can pass a **Flow token** and data for the first screen, such as a name or an order number to show.

> [!NOTE]
>
> **In Flowella.** After you sync a form, click **Create template with this Flow** to open the editor with the Flow button connected. Through the API, `buttonParameters` can set the Flow token and pass first-screen data with `flowActionData`. A template keeps opening the Flow version it was built with. To send a newer Flow version, update the template. See [Send the Flow to customers](https://knowledge.flowella.io/app/flows.md#send-the-flow-to-customers).

## An interactive Flow message

Inside the window, you can send a Flow as an interactive message with a header, body, footer and a button label. Meta advises button text of 30 characters or fewer, with no emoji. You choose the first screen and its data, and whether to send the published or draft version.

Flowella doesn't offer this. Inside the window, send the same template from the inbox instead.

## What the customer sees

1. The message, with the button label you chose.
2. When they tap it, the first screen slides up over the chat.
3. When they finish, a confirmation appears in the chat, and you receive their answers.

If the customer's app can't show Flows, the message can't be delivered. See [Flow client support](https://knowledge.flowella.io/whatsapp/flows/flows-client-support.md).

## Before you send at scale

* **Test on a phone.** Send the template to yourself, open the Flow and submit it. Check the answers arrive where you expect. See [Test a template](https://knowledge.flowella.io/app/templates.md#test-a-template).
* **Check Meta's requirements.** Sending Flows needs a verified business and a good quality rating. See [WhatsApp Flows overview](https://knowledge.flowella.io/whatsapp/flows/flows-overview.md#what-meta-requires).
* **Watch the Flow's health** if it uses an endpoint. A throttled Flow can be sent only 10 times an hour. See [Flow health](https://knowledge.flowella.io/whatsapp/flows/flow-health.md).

## Related

> [card] [Send your first Flow](https://knowledge.flowella.io/send-your-first-flow.md)
>
> From HubSpot form to first send.

> [card] [Send WhatsApp Template](https://knowledge.flowella.io/hubspot/workflow-actions.md#send-whatsapp-template)
>
> Send a Flow from a HubSpot workflow.

> [card] [Bulk send](https://knowledge.flowella.io/app/bulk-send.md)
>
> Send a Flow to a list.

> [card] [Flows error codes](https://knowledge.flowella.io/whatsapp/errors/flows-error-codes.md)
>
> When a send or publish fails.

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


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