The WhatsApp native Integration lets you connect a WhatsApp Business Account to Blueshift and use WhatsApp as a campaign channel. This article covers prerequisites, adapter setup, and how to connect your account via Meta's Embedded Signup.
The WhatsApp integration is available under Instant Messaging in App Hub.
Enable WhatsApp for your account
Contact support@blueshift.com to enable WhatsApp on your account.
Before you start
| Requirement | Details |
|---|---|
| Meta Business portfolio | You select this during setup to associate your WhatsApp Business assets with Blueshift. If you don't have one, create one at Meta Business Suite before proceeding. |
| Admin access to your Meta business assets | Required to complete Meta Embedded Signup and share business assets with Blueshift during setup. |
| WhatsApp Business Account (WABA) | Select an existing WABA or create one during Embedded Signup. Review Meta's current account and messaging limits before rollout. |
| WhatsApp sender phone number | The sender's number that customers see when they receive messages from your business. If the number is currently registered with another WhatsApp provider, ask that provider to disable 2FA on the number before you begin. Meta will migrate it to this integration during Embedded Signup. Review Meta's business phone number requirements before setup. |
| Valid WhatsApp display name | Appears on your WhatsApp Business profile and in customer conversations. Review Meta's display name guidelines before adding or selecting a number. |
| Approved WhatsApp message templates | Create and submit templates for approval in Meta WhatsApp Manager. Blueshift syncs approved templates into WhatsApp Templates; templates cannot be created or submitted from within Blueshift. |
| Blueshift setup assistance | Contact Blueshift Support before you begin. The Blueshift implementation team enters and saves the required credentials. You then complete the Facebook signup step using your own Meta Business portfolio — no login or credential sharing with Blueshift is required. |
Open WhatsApp in App Hub
- Go to App Hub in the left navigation panel.
- Under Explore, click Instant Messaging.
- Select WhatsApp.
- Click Configure. The WhatsApp configuration page opens, listing the active and archived adapters on your account.
Create the adapter
Contact Blueshift before you begin
The Blueshift implementation team enters the required credentials into the adapter. Reach out to Blueshift Support to arrange this before the steps below.
- On the configuration page, click + Adapter.
- Enter a name for the adapter.
Once the Blueshift implementation team enters and saves the credentials in the Authorization section, the Sign up with Facebook button becomes active.
| Fields filled in by Blueshift | Description |
|---|---|
| Project ID | Project identifier. |
| Client ID | Credential identifier. |
| Client Secret | Secure key. Masked after entry. |
| Region | Region for your account. |
Complete Facebook signup
Click Sign up with Facebook. A Facebook login pop-up opens and guides you through Meta Embedded Signup.
During the Meta flow:
- Review the permissions and click Continue.
- Select the Business portfolio to connect, or create a new one.
- Select an existing WhatsApp Business Account, or create a new one.
- Add your WhatsApp phone number. The options available depend on your Meta account.
- Complete the remaining steps in the pop-up.
Meta controls this flow
The screens you see depend on your existing WhatsApp Business Accounts, phone numbers, permissions, and verification status. If you are unsure about any step, refer to Meta's Embedded Signup documentation or contact Blueshift Support.
Confirm the connection
After the Embedded Signup is complete, the adapter page displays Connected to WhatsApp and auto-populates the following fields:
| Field | Description |
|---|---|
| WhatsApp Business Account ID (WABA ID) | The WhatsApp Business Account connected through Embedded Signup. |
| Phone Number | The sender phone number associated with this adapter. |
| Business ID | The Meta business ID connected during signup. |
If the connection was not established
If the adapter page does not show Connected to WhatsApp after completing the Meta flow, do not attempt to run the signup again. See Troubleshooting below, or contact Blueshift Support.
Troubleshooting
For anything not listed here, contact your Blueshift Support with a screenshot and any further details about the error.
| Error/scenario | What it means | What to do |
|---|---|---|
| To use this phone number, you'll need to delete an existing one or request additional numbers. | Your WABA has reached its phone number limit. | In Meta Business Suite, remove a phone number you are not using, or request additional numbers from Meta. See Meta's messaging limits. Then run signup again. |
| This number is registered to an existing WhatsApp account. | The number is active on another WhatsApp account — the consumer app or another business provider. | If the number is on the WhatsApp consumer app, delete that account from WhatsApp's settings on the device, wait a few minutes, then run signup again. If it is with another business provider, ask them to disable 2FA on the number — Meta will then migrate it during Embedded Signup. See Meta's business phone number requirements. |
| Facebook signup pop-up does not open | The browser is blocking the pop-up. | Allow pop-ups for the Blueshift domain in your browser settings and try again. |
| Adapter page spins and resets to empty after completing Meta signup | Setup completed on WhatsApp's side, but the confirmation did not reach Blueshift. | Do not click Sign up with Facebook again — it will produce an additional error. Contact Blueshift Support with the phone number and the time this happened. |
| Still connecting your WhatsApp account (N seconds elapsed). Don't click Sign up with Facebook again. | WhatsApp sender registration is taking longer than expected. | Wait a few minutes and refresh the adapter page. Do not click Sign up with Facebook again — doing so can produce a "phone number already in use" error. If the adapter still shows as unconnected, contact Blueshift Support. |
| WhatsApp connection failed: This phone number is already in use. Choose a different number. | The phone number is already associated with a WhatsApp sender in this integration. | Choose a different phone number during Embedded Signup. If you believe this number should be available, contact Blueshift Support. |
| WhatsApp connection failed: No WhatsApp Business Account selected. Click Sign up with Facebook again and select your business. | No WhatsApp Business Account was selected during the Meta flow. | Click Sign up with Facebook again and make sure you select a business account and complete every step. |
| WhatsApp connection failed: This WhatsApp Business Account is connected to another provider. Disconnect it there first. | The selected WABA is already in use with another messaging provider. | Ask the other provider to disable 2FA on the phone number. Once disabled, Meta will migrate it during Embedded Signup and you can use the same phone number to set up your adapter in Blueshift. |
| WhatsApp connection failed: Connection credentials weren't accepted. | The credentials entered during adapter setup weren't accepted. | Contact Blueshift Support — the Blueshift implementation team will need to verify and re-enter the credentials. |
| WhatsApp connection failed unexpectedly. Try again, or WhatsApp setup didn't complete. | A temporary error occurred during setup. | Wait 5 minutes and try again. If the error persists, contact Blueshift Support with a screenshot. |
| Any other error | — | Contact Blueshift Support. |
Manage WhatsApp adapters
The WhatsApp configuration page lists all active adapters on your account. Each adapter represents one WhatsApp sender phone number. To open it, go to App Hub > Instant Messaging > WhatsApp > Configure.
Each adapter row has the following controls:
- Edit Adapter — View the adapter's connection details. To update credentials, contact Blueshift Support.
- Archive — Moves the adapter to the Archived Adapters section at the bottom of the page. To restore it, click Unarchive.
- Delete — Permanently removes the adapter.
Archiving or deleting impacts templates
Every WhatsApp template requires a WhatsApp sender adapter. If that adapter is archived or deleted, the template has no sender and will fail to send when triggered in a campaign.
Archived — The adapter is inactive but recoverable, and is listed at the bottom of the adapter configuration page. Click Unarchive to restore it.
Deleted — The adapter is permanently removed.
Next steps
With the adapter connected, opt in your customers and sync your approved WhatsApp templates into Blueshift. Create and submit templates for approval in Meta WhatsApp Manager, then sync them into Blueshift to personalize and use in campaigns. See WhatsApp overview to get started.
Comments
0 comments