Connect WhatsApp in manual mode (Phone Number ID and token)
For advanced cases, Omnifox lets you connect a WhatsApp Cloud API number by pasting its credentials by hand instead of using Meta's wizard.
Manual mode is meant for technical teams or operations that already have a WhatsApp Cloud API number set up on another platform and want to bring it to Omnifox without going through Meta's wizard (Embedded Signup). It is an advanced setup, collapsed by default.
Requirements
- An existing WhatsApp Cloud API number with its Phone Number ID, Business Account ID and an access token (ideally a permanent one from a Meta Business Manager System User).
- Admin permissions in your Omnifox workspace.
Steps
- Go to Settings → Channels and click Connect New Channel. Pick WhatsApp.
- Type a channel name (required).
- Choose one of the two Cloud API options — Migrate existing number or Create a new Cloud API number. The manual block lives below the Meta flow, not on the three-card screen.
- Expand the "Configuración manual (Avanzado)" accordion. (This label is still shown in Spanish.)
- Fill in Phone Number ID and Business Account ID exactly as they appear in Meta Business Manager.
- Paste the Access Token (no need for the App Secret — Omnifox applies it automatically).
- Copy the Verify Token Omnifox generated and paste it into the Webhooks section of your Meta app.
- Copy the Webhook URL shown and configure it in the same place in Meta.
- Optional: fill in the Catalog ID if you plan to send Meta Commerce catalogue products from the composer.
- Save. The channel goes active as soon as Meta confirms the webhook subscription.
Unlike the Embedded Signup flow —where the webhook registers itself— in manual mode you configure the webhook yourself in Meta. That's the step people forget most.
Example
A team migrating from another WhatsApp Cloud API provider pastes their existing Phone Number ID and System User token, configures the webhook in Meta with the values Omnifox generated, and the number starts receiving messages in the inbox without going through the standard onboarding flow.
Tips
- Always use a permanent System User token, not a temporary user token that expires.
- Store the Verify Token somewhere safe — you need it every time you reconfigure the webhook in Meta.
Troubleshooting
If the channel saves but no messages arrive, confirm in Meta that the webhook was verified with the right Verify Token and that the subscribed fields include messages.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.