Productivity

Bubble WhatsApp Integration With the API Connector (No Plugin)

You do not need a plugin to send WhatsApp messages from Bubble. The built-in API Connector, one private header and one send call are enough.

Daniel Roth7 min read

Bubble WhatsApp Integration With the API Connector (No Plugin)
On this page

Short answer: In Bubble, open the API Connector and add an API with the authentication set to "Private key in header". Use Authorization as the key name and Bearer bt_live_... as the value. Then add a call that does POST https://api.blueticks.co/v1/scheduled-messages/{chatId} with a JSON body of {"type":"text","text":"..."}, initialize it, and use it as an Action in a workflow. The message goes out from your own WhatsApp number.

There is no Blueticks plugin to install, and you do not need one. Bubble's API Connector is built in, and Blueticks is a plain REST API with a bearer key. The Blueticks side of this guide was checked against the backend on 2026-11-22. The Bubble side follows Bubble's own manual, and menu labels can change, so match on meaning if one differs.

What do you need first?

  • A Blueticks API key. Create it on the API page of the dashboard, app.blueticks.co/blueticks-api. It starts with bt_live_.
  • A connected WhatsApp. Your number has to be linked in Blueticks. GET /v1/ping returns api: "ok" and a whatsappConnections list, which is empty when nothing is connected.
  • A paid plan, if the app will send regularly. An account with no active subscription gets 5 API requests per six-hour window.

How do you set up the API in the API Connector?

Add a new API and give it a name. Bubble puts the collection name in your app's client-side source, so keep it neutral, like Blueticks.

Set Authentication to Private key in header. Per Bubble's manual, the fields are:

  1. Key name: Authorization
  2. Private key: Bearer followed by your key, with a space after Bearer. Bubble's docs say that if the provider expects a prefix such as Bearer, you put it before the key, separated by a space.

Setting the key at this level is the point. The Bubble manual warns that values marked Private under "None or self-handled" authentication are exposed, and recommends keeping credentials in a collection that uses a method such as Private key in header. That is the setup here. Leave the key out of the call's body and out of any page element.

How do you add the send call?

Add a call to that API:

  • Name: Send message
  • Use as: Action. Bubble's docs say Data calls show up in "Get data from an external API" and Action calls appear in the Plugins section of the Actions dropdown, and sending is an action.
  • Method and URL: POST https://api.blueticks.co/v1/scheduled-messages/ plus the recipient. The recipient is the last path segment and can be a phone number such as +15551234567 or a group id ending in @g.us. Make it a dynamic value, since it changes on every call.
  • Body type: JSON
  • Body: {"type":"text","text":"Your order is ready"}, with the text as a dynamic value. How you mark a value as dynamic is covered in Bubble's page on adding calls.

Omit sendAt and the message goes out now. Add sendAt (RFC 3339, at least 10 seconds ahead) and it is delivered later.

Why does the Initialize call matter so much here?

Bubble requires every call to be initialized before you can use it, and initialization makes a real request. Bubble's manual says initialization calls "may produce actual outcomes, including the modification of live data."

For this call that means pressing Initialize call sends a real WhatsApp message. Point it at your own number with a short test text. Do not initialize it against a customer's chat or a group.

When it succeeds, Bubble reads the response and creates typed fields from it. The send call returns the message wrapped as { "success": true, "data": { ... } }. A 201 means it was sent. A 202 means WhatsApp had not confirmed it within about 50 seconds, and the response carries an id and a statusUrl you can check later instead of sending again.

How do you send from a workflow?

In any workflow, add an action and look under Plugins for the call you just created. Fill in the recipient and the text from your page data, for example the phone field of a Thing in your database.

To make a retry safe, add an Idempotency-Key header to the call (up to 64 characters). Two requests with the same key send one message.

How do you get replies back into Bubble?

Use a webhook. Register one with the Blueticks API, and point it at a Bubble backend workflow. In Bubble:

  1. In Settings, API, check Enable Workflow API and backend workflows.
  2. Create a backend workflow and tick Expose as a public API workflow. Its URL looks like https://yourdomain.com/api/1.1/wf/workflow_name.
  3. Use Detect data and send a test POST to the URL with /initialize added, so Bubble learns the fields.
  4. If the sender expects a 200 even when a condition is not met, tick Bubble's option to return 200 in that case.

I could not confirm from Bubble's manual which plans include the Workflow API, so check that on your own plan before you build on it. The Blueticks side, including how to register the webhook, how events are shaped and how to check them, is in WhatsApp webhooks and auto-reply.

What can go wrong?

  • Nothing sends. Call GET /v1/ping and check that whatsappConnections is not empty.
  • A 401. The header value is missing Bearer or the key is wrong. Check the space.
  • A 429. You are over a rate limit. Sends are limited to 60 per minute per key, and the response includes a Retry-After header.
  • A 403. The key lacks a scope for that call. Create the key with Full access (the dashboard default); a Read-only key gets a 403 on sends.
  • Group sends. Use the group's id as the recipient. To look ids up, call GET /v1/groups, covered in the group API guide.

If you would rather skip building it yourself, the full REST API guide shows the same calls in curl and Python.

FAQ

Is there a Bubble plugin for Blueticks? No. This guide uses the API Connector that comes with Bubble.

Does this use the official WhatsApp Business API? No. It sends through your own WhatsApp number via a connected Blueticks engine, so there is no Meta business verification or template approval.

Can Bubble send to a group? Yes. A group id ending in @g.us works as the recipient, the same as a phone number.

Share this article

Want more WhatsApp recipes? Join the free WhatsApp Growth Recipes community.

The Dispatch, every week.

One sharp WhatsApp growth tactic in your inbox each week. Joined by 238,000+ founders, marketers and support leads.

Free forever. No spam, unsubscribe in one click.

Also on TikTok: @blueticksagents