How to connect WhatsApp to n8n ​

AvenPing can share your WhatsApp Cloud API credentials with n8n so workflows send on that line and the WhatsApp Trigger receives inbound messages. Open Integrations, activate n8n (badge Automation), copy Access Token and WhatsApp Business Account ID into n8n credentials, then save the Trigger webhook as Callback URL.

Prerequisites ​

Step-by-step ​

  1. Open the n8n card
    Sign in at app.avenping.com. Click Integrations. Find n8n (badge Automation, description WhatsApp Business Cloud credentials and Trigger webhook for n8n.). Click Activate, or Configure if the card already shows Active. Follow Official setup (n8n WhatsApp Business Cloud credentials).

  1. Set Share scope
    Under Share scope, choose Entire WhatsApp Business Account or Single phone number. Select WhatsApp Business Account. Use Single phone number when the workflow should only see one line. If the WABA list is empty, connect a WABA first and refresh Integrations.

  2. Create n8n sending credentials
    Under Sending messages, copy Access Token and WhatsApp Business Account ID. In n8n, create WhatsApp Business Cloud credentials: paste Access Token as Access Token and WhatsApp Business Account ID as Business Account ID. Use these credentials on the WhatsApp Business Cloud node. Pause or an expired plan only stops webhook forwarding; the token itself stays valid.

  3. Wire the WhatsApp Trigger webhook
    For inbound messages, n8n’s WhatsApp Trigger uses OAuth-style Client ID and Client Secret. Copy AvenPing App ID → n8n Client ID and App Secret → n8n Client Secret. Add a WhatsApp Trigger, copy its webhook URL, and paste it into AvenPing Callback URL (placeholder https://your-n8n.host/webhook/whatsapp). Set the same Webhook Verify Token on both sides (placeholder Shared token (required for handshake)).

  4. Save and Test in AvenPing
    Click Save (Webhook config saved), then Test. Success is Webhook connection succeeded. Status should read Active. Use Pause to stop forwarding (Webhook forwarding paused) and Resume to start again. Click Regenerate app secret only if you must rotate Client Secret in n8n.

WARNING

Do not paste AvenPing Settings → Webhook Settings URLs into n8n. That Settings page is AvenPing’s outbound webhook to your server, not the Cloud API share callback.

TIP

Sending uses the Cloud node (Access Token + Business Account ID). Receiving uses the Trigger webhook plus App ID / App Secret. You usually need both.

FAQ ​

Which n8n credential type do I use?

WhatsApp Business Cloud (API key) for sending: Access Token and Business Account ID. WhatsApp Trigger (OAuth2) for receiving: Client ID = App ID, Client Secret = App Secret.

Why does Test say Handshake did not return the challenge?

The Trigger must be listening and must use the same Webhook Verify Token you saved in AvenPing. Activate the workflow, then click Test again.

What if Status is Blocked (plan / credit line)?

AvenPing stops forwarding inbound webhooks. Sending from n8n with the copied Access Token can still work until you rotate it. Restore the plan or credit line, then Resume.