Connect WhatsApp

Objective. Connect your own WhatsApp Business Account and phone number with manually entered Meta Cloud API credentials that Fluenta verifies on save.

Prerequisites

A Fluenta workspace owner account. The WhatsApp connection setting is owner-only.
Your own Meta WhatsApp Business Account and WhatsApp phone number. Fluenta does not provision or resell numbers.
The Phone number ID, access token, app secret, and, when you need templates, subscriptions, or analytics, the WhatsApp Business Account ID from Meta.

Use the manual connection path

Fluenta connects through Meta’s official WhatsApp Business Platform (Cloud API). Meta Embedded Signup does not exist in Fluenta, and there is no one-click Facebook connect. You paste the credentials for your own Meta app and account.

For the full Meta-side setup story, including the work you must complete in Meta Business Manager, read WhatsApp onboarding. You can still design and test a flow before doing any of this Meta setup.

Paste credentials and subscribe the webhook

1Open the bot editor, select Settings, and choose WhatsApp.
2In Meta credentials, paste the Phone number ID and Access token from Meta app → WhatsApp → API Setup. Paste the App secret from Meta app → App settings → Basic.
3Paste the WhatsApp Business Account ID from Meta app → WhatsApp → API Setup. This field is optional for the credential save itself, but templates, subscriptions, and analytics need it.
4Select Save credentials. Fluenta validates that the Phone number ID, access token, and app secret are present, then verifies the connection against Meta before it completes the save.
5After you save a WhatsApp Business Account ID, use Subscribe in the Meta app webhook card. Fluenta subscribes that account to the shared webhook; the button remains unavailable until a WABA ID is saved.

Understand how Fluenta handles connection secrets

Fluenta encrypts the access token and app secret at rest with AES-256-GCM. Incoming Meta webhooks are verified with an HMAC-SHA256 signature over the raw body using the x-hub-signature-256 header; a signature mismatch is rejected.

Expected result

Expected result. Your Meta credentials are saved for this bot, the Meta connection card can show the verified connection details, and a saved WABA ID enables the shared webhook subscription. The access token and app secret are not stored as plain text.

Common errors

Phone number ID, access token, and app secret are required.: Fill all three required fields in Meta credentials. The WhatsApp Business Account ID can be empty for the initial credential save, but it is needed for templates, subscriptions, and analytics.
Meta rejects the credential save.: Check the token and Phone number ID in Meta. A fatal Meta verification failure, such as an invalid token or unknown phone number, rejects the save and leaves the previous credentials unchanged.
This phone number is already connected to another bot.: A phone number can be connected to only one bot. Use a different phone number or disconnect it from the other bot first.
Subscribe is disabled or templates are unavailable.: Add the WhatsApp Business Account ID, save it, then return to the Meta app webhook card. The WABA ID is required for subscriptions, templates, and analytics.
I expected Meta Embedded Signup or a Facebook connect button.: Neither exists in Fluenta. Follow the manual credential flow above and use WhatsApp onboarding for the Meta-side requirements.