Flowella sits between your CRM and Meta’s WhatsApp Business Platform. This page explains, at a high level, where each piece lives and how data moves between them.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.
The three systems
HubSpot
Your source of truth for contacts, forms, properties, and workflows.
Flowella
Bridges HubSpot and WhatsApp. Owns Flows, templates, the inbox, opt-outs, and the API.
Meta (WhatsApp)
Hosts your WABA, phone numbers, templates, and the WhatsApp Business Platform itself.
Data flow at a glance
A typical end-to-end interaction looks like this:Trigger
A HubSpot workflow, a click-to-WhatsApp ad, or a contact messaging your number kicks things off.
Flowella decides what to send
Flowella checks opt-in status, selects the right template or Flow, and resolves any variables from HubSpot properties.
Meta delivers the message
Flowella sends the message via Meta’s WhatsApp Business Platform. The contact receives it on WhatsApp.
The contact responds or completes a Flow
Replies and Flow submissions come back through Meta’s webhooks to Flowella.
What lives where
| Concern | System |
|---|---|
| Contact records, forms, properties, lists, workflows | HubSpot |
| WABA, phone numbers, templates, display name, message delivery | Meta |
| Flow ↔ form mapping, inbox, opt-outs, API keys, webhooks, billing | Flowella |
Authentication boundaries
- HubSpot is connected via OAuth. You authorise Flowella once during onboarding; the connection is stored at the org level.
- Meta is connected through Meta’s Embedded Signup. Flowella stores the long-lived access tokens needed to operate the WABA.
- The Flowella API is authenticated with API keys you create in Settings → API keys.
- Outbound webhooks from Flowella are signed so you can verify requests came from us. Configure them in Settings → Webhooks.
Multi-channel and multi-WABA
A single Flowella org can host multiple WABAs and multiple phone numbers. Most app pages are scoped to one channel — you will see the URL change to/{org}/{waba}/{phone}/… when you pick a channel. See Multi-channel and multi-WABA for how to switch between them.