How to connect WhatsApp Cloud API to Chatwoot ​

AvenPing shares your Cloud API line with Chatwoot through the manual WhatsApp inbox (not Embedded Signup). Open Integrations, activate Chatwoot (badge Inbox), paste Phone Number ID, WhatsApp Business Account ID, and Access Token into Chatwoot, then save Chatwoot’s webhook URL and verification token in AvenPing.

Prerequisites ​

Step-by-step ​

  1. Open the Chatwoot card
    Sign in at app.avenping.com. Click Integrations. Find Chatwoot (badge Inbox, description Manual Cloud API inbox: Phone ID, WABA ID, token, webhook.). Click Activate, or Configure if the card already shows Active. Follow Official setup on the page for Chatwoot’s manual channel article.

  1. Set Share scope to a single number
    Under Share scope, choose Single phone number, then select WhatsApp Business Account and Phone number. Chatwoot inboxes are per number; the callback placeholder is https://your-chatwoot-domain/webhooks/whatsapp/{phone_number}. Entire WhatsApp Business Account still copies the WABA token, but inbound filtering should match the inbox’s phone.

  2. Create the Chatwoot manual inbox
    Under Sending messages, copy Phone Number ID, WhatsApp Business Account ID, and Access Token. In Chatwoot, go to Settings → Inbox, choose the manual WhatsApp flow, and paste those values (plus the phone number Chatwoot asks for). Do not start Embedded Signup — that flow tries to create a new Meta connection instead of using AvenPing’s share.

  3. Save Chatwoot’s webhook in AvenPing
    Chatwoot shows a webhook URL and webhook verification token after you create the inbox. Paste them into AvenPing Callback URL and Webhook Verify Token. Click Save (Webhook config saved), then Test. Success is Webhook connection succeeded. If the handshake fails, you see Handshake did not return the challenge.

  4. Confirm Active and keep secrets in sync
    Status should read Active. Use Pause / Resume to stop or restart forwarding. App ID and App Secret are not required for Chatwoot’s manual inbox fields; leave them in AvenPing unless Chatwoot asks for them later. Regenerate app secret is only needed if a later Chatwoot screen stores App Secret.

WARNING

Embedded Signup in Chatwoot is a different product path. This AvenPing card is for the manual Cloud API inbox only.

TIP

The callback includes {phone_number}. Copy the exact URL Chatwoot prints; do not invent the host or the phone segment.

FAQ ​

Which Chatwoot fields map to AvenPing?

Phone Number ID → Chatwoot phone number ID. WhatsApp Business Account ID → business ID. Access Token → access token. Then Chatwoot’s webhook URL / verification token go back into AvenPing Callback URL and Webhook Verify Token.

Why would Test fail?

The inbox must exist and Chatwoot must answer the challenge with the same verification token. Save both sides, then click Test. Empty Callback URL toasts Save the webhook first.

Does Pause stop Chatwoot from sending?

No. Pause only stops AvenPing from forwarding inbound webhooks. Chatwoot can still send with the copied Access Token until you revoke or replace it.