Skip to content

How to share WhatsApp Cloud API credentials from AvenPing

AvenPing can share the WhatsApp Cloud API credentials you already connected so Odoo, ERPNext / Frappe, n8n, BoldDesk, or Chatwoot can send and receive on that line. Open Integrations, activate the product card, then follow that product’s tutorial — paste destinations differ even though the AvenPing configurator looks the same.

Prerequisites

Step-by-step

  1. Open Integrations
    Sign in at app.avenping.com. Click Integrations. Cloud API share cards are Odoo (badge ERP), ERPNext / Frappe (badge ERP), n8n (badge Automation), BoldDesk (badge Support), and Chatwoot (badge Inbox). Payment cards and Zoho CRM are separate configurators.
  1. Activate the product card
    Click Activate, or Configure if the card already shows Active. AvenPing opens Share scope, Sending messages, and Receiving messages. If no WABAs appear, connect a WABA first; the hint is Connect a WhatsApp Business Account first, then refresh this page.

  2. Follow the tutorial for that product
    Paste destinations are not interchangeable. Use:

  3. Save callback and Test
    On every card, Receiving messages needs Callback URL and Webhook Verify Token. Click Save (Webhook config saved), then Test. Success is Webhook connection succeeded. Status may be Active, Paused, Inactive, or Blocked (plan / credit line).

WARNING

Razorpay, Stripe, Cashfree, and Zoho CRM are not Cloud API share cards. Do not use this flow for payments or CRM sync.

TIP

Pause only stops webhook forwarding. The copied Access Token stays valid until you rotate it.

FAQ

Which products use this share flow?

Odoo, ERPNext / Frappe, n8n, BoldDesk, and Chatwoot. Each has its own how-to. Payment cards and Zoho CRM use different screens.

Is the AvenPing UI different per product?

The configurator is the same: Share scope, Sending messages (App ID, App Secret, Phone Number ID, WhatsApp Business Account ID, Access Token), and Receiving messages. Official setup, Callback URL placeholder, and where you paste on the other product change.

Why does Test fail?

The other product must answer the webhook challenge with the same Webhook Verify Token. Save both sides, then click Test again.