Skip to article

Integrations

WhatsApp

A usable WhatsApp Business Cloud API number and a chat with the Obelo number

Ownership and availability

You own the WhatsApp Business account and number. Obelo manages the Cloud API webhook and links your chat using a short-lived code.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect

  • WhatsApp updates are available in Obelo
  • Your website's company intelligence is ready
  • An Obelo owner, admin, strategist, or editor may link the chat

Connect an existing account

  1. Open the provider in Settings → Integrations for the intended website.
  2. Generate a short-lived link code in Obelo
  3. Send the exact link command to the Obelo WhatsApp number
  4. Return before the code expires and check the status

If you need a new resource

  1. Install WhatsApp and create or select the account that should receive Obelo messages
  2. Start a chat with the Obelo WhatsApp number
  3. Return to Obelo to generate the website-scoped link code

Permissions to check

  • Obelo links a chat identity; it never asks for your WhatsApp password
  • Outbound business messages may require approved templates under Meta's messaging rules

Verify and troubleshoot

Return after sending the command and use Check status before the code expires.

The WhatsApp link is not active yet. Confirm the command was sent to the correct Obelo number before the code expired.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.

Something unclear or out of date?

Suggest a correction