One engine in the middle of your whole stack.
Flowella connects WhatsApp and HubSpot natively, plugs into Meta ads for Click-to-WhatsApp, and exposes a REST API and webhooks for everything else. So a conversation that starts on WhatsApp can reach your CRM, your automation and the rest of your tools, without glue code holding it together.
Native where it counts, open everywhere else.
HubSpot and WhatsApp are native connections, not bolt-ons. Meta ads feed in through Click-to-WhatsApp, and your HubSpot workflows can send templates and Flows directly. Anything without a native connector, your other tools, an internal system, an automation platform like n8n or Zapier, connects through the API and webhooks. Flowella sits in the middle, so the conversation and its data can flow wherever they need to.
The connections at a glance
The native connections do the heavy lifting; the API reaches everything else.
| Connection | What it does | How it connects |
|---|---|---|
| HubSpot CRM | Two-way sync of contacts, Flow answers and activity | Native |
| HubSpot workflows | Send templates and Flows as workflow actions | Native |
| WhatsApp Business Platform | The channel that carries every message and Flow | Native |
| Meta ads | Click-to-WhatsApp ads that open a Flow | Native |
| HubSpot conversations inbox | WhatsApp threads alongside email, chat and calls | Custom channel |
| n8n, Zapier, custom systems | Whatever your stack needs beyond the above | API and webhooks |
Native connections, and the open API.
Honest about the line: some things are built in, the rest you connect yourself through the API.
The connections we maintain.
The core of your funnel, HubSpot, WhatsApp and Meta ads, is built in and supported by us. You configure it in the app, with no code and no third-party glue to keep alive.
- HubSpot CRM and workflows
- WhatsApp Business Platform
- Meta Click-to-WhatsApp ads
Everything else, through the API.
Where there is no native connector, the REST API and webhooks let you wire Flowella into anything: a data warehouse, a bespoke app, or an automation platform you already run.
- Any tool with no native connector
- Internal and bespoke systems
- n8n, Zapier and similar platforms
- ⏱️ 30 seconds · Card on file
- 👤 With · Membership team
- 📩 Receipt sent here after renewal
Choose your plan
- 🏆 Annual · £49 ✓
- 🎯 Quarterly · £15 ✓
- 📅 Monthly · £6 ✓
Powered by Flowella · Secure renewal
Straight answers.
The questions teams ask about connecting Flowella.
Which connections are native?
HubSpot and the WhatsApp Business Platform are native, two-way connections. Meta ads connect through Click-to-WhatsApp, and HubSpot workflows can send templates and Flows directly.
How do I connect a tool that is not listed?
Through the REST API and outbound webhooks. If a tool has no native connector, you can still wire it to Flowella by calling the API and reacting to webhook events.
Can I use n8n or Zapier?
Yes. They connect via the API and webhooks rather than a native connector, which is the right place for automation platforms, since you control the logic.
How does WhatsApp appear inside HubSpot?
It becomes a custom channel in the HubSpot conversations inbox, so WhatsApp threads sit alongside email, chat and calls. See the Inbox page for detail.
Do I need to maintain glue code?
No glue code for the native connections, they are configured in the app. For anything you connect via the API, you write only the integration code specific to your own system.
What if I need a connection you do not have?
Tell us through support. We add native connections and webhook events as customers ask for them, so the list grows with demand.
Go deeper on any connection
Each connection has its own page or doc with the full detail.
The deeper detail for each connection lives across the product pages and the knowledge base.
For the developer route, see API and webhooks on this site, or the API reference in the docs. For WhatsApp inside HubSpot, see the Inbox page. For paid social, see Click-to-WhatsApp ads.
