> ## 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 Flowella fits together

> A high-level view of how data, messages, and webhooks move between HubSpot, Flowella, and Meta's WhatsApp Business Platform across the full integration.

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.

## The three systems

<CardGroup cols={3}>
  <Card title="HubSpot" icon="database">
    Your source of truth for contacts, forms, properties, and workflows.
  </Card>

  <Card title="Flowella" icon="workflow">
    Bridges HubSpot and WhatsApp. Owns Flows, templates, the inbox, opt-outs, and the API.
  </Card>

  <Card title="Meta (WhatsApp)" icon="message-circle">
    Hosts your WABA, phone numbers, templates, and the WhatsApp Business Platform itself.
  </Card>
</CardGroup>

## Data flow at a glance

A typical end-to-end interaction looks like this:

<Steps>
  <Step title="Trigger">
    A HubSpot workflow, a click-to-WhatsApp ad, or a contact messaging your number kicks things off.
  </Step>

  <Step title="Flowella decides what to send">
    Flowella checks opt-in status, selects the right template or Flow, and resolves any variables from HubSpot properties.
  </Step>

  <Step title="Meta delivers the message">
    Flowella sends the message via Meta's WhatsApp Business Platform. The contact receives it on WhatsApp.
  </Step>

  <Step title="The contact responds or completes a Flow">
    Replies and Flow submissions come back through Meta's webhooks to Flowella.
  </Step>

  <Step title="Flowella writes the result back to HubSpot">
    Form submissions, Flow responses, and conversation activity sync to the corresponding HubSpot contact, triggering any HubSpot workflows you have set up.
  </Step>
</Steps>

## 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](/essentials/multi-channel) for how to switch between them.

<Tip>
  If you are evaluating Flowella for a technical buyer, pair this page with [Data security](/security/data-security).
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Multi-channel" icon="layers" href="/essentials/multi-channel">
    How channels, WABAs, and phone numbers map onto Flowella URLs.
  </Card>

  <Card title="Glossary" icon="book" href="/essentials/glossary">
    Definitions for WABA, channel, conversation, template, and more.
  </Card>

  <Card title="API introduction" icon="code" href="/api-reference/introduction">
    Auth, errors, rate limits, and pagination.
  </Card>

  <Card title="Status and incidents" icon="activity" href="/essentials/status-and-incidents">
    Triage when something is wrong on Flowella, Meta, or HubSpot.
  </Card>
</CardGroup>