🇪🇸 Español 🇬🇧 English 🇧🇷 Português

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.

Jul 11, 2026

Manual mode is built for technical teams or operations that already have a WhatsApp Cloud API number configured on another platform and want to bring it into Omnifox without going through Meta's wizard (Embedded Signup). It's an advanced setting, hidden by default.

Requirements

  • Your organization needs manual configuration enabled (turned on by an Omnifox superadmin for specific cases).
  • 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).

Steps

  1. Under Channels → Connect channel → WhatsApp, expand the "Manual configuration (Advanced)" accordion.
  2. Fill in Phone Number ID and Business Account ID exactly as they appear in Meta Business Manager.
  3. Paste the Access Token (no need to paste the App Secret — Omnifox applies it automatically).
  4. Copy the Verify Token Omnifox generated and paste it into your Meta app's Webhooks configuration.
  5. Also copy the Webhook URL shown and set it in the same place on Meta.
  6. Optional: fill in Catalog ID if you'll be sending Meta Commerce catalog products from the composer.
  7. Save — the channel goes active as soon as Meta confirms the webhook subscription.

Example

A team migrating from another WhatsApp Cloud API provider pastes the existing Phone Number ID and System User token, sets up the webhook in Meta with the data 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.
  • Keep the Verify Token somewhere safe — you'll need it every time you reconfigure the webhook on Meta.

Troubleshooting

If the channel saves but no messages come through, confirm in Meta that the webhook was verified with the correct Verify Token and that the subscribed fields include messages.

Was this helpful?

Related articles