Integrate WAWCD Plugin Receive Message with

1000+ apps and services

How it works?
nbound flow

You add WAWCD Plugin Receive Message to a workflow and copy its webhook URL.
In WAWCD → Outgoing Webhooks, you register that URL (POST).
When a contact messages your WAWCD-connected WhatsApp account, WAWCD sends JSON to n8n.
The node normalizes field names (including reciver-* → receiver-*) and passes data to the next nodes.
Outbound flow

You create WAWCD API credentials in n8n (API base URL + incoming webhook token).
You add WAWCD Plugin Send Message and configure recipient(s) and content.
The node POSTs to {API Base URL}/webhooks/send-message with Authorization: Bearer <token>.
WAWCD delivers the message through WhatsApp Web (extension must be online).
The WhatsApp account is tied to your incoming webhook token on the WAWCD backend — you do not pass a separate account ID in the send body.

Features
WAWCD Plugin Receive Message (Trigger)
Webhook trigger with Test URL (while editing) and Production URL (when workflow is active)
Optional custom Path segment for the webhook URL
Incoming Authentication — none, or shared secret via Authorization: Bearer or X-WAWCD-Token
Strict Payload Validation — reject requests that do not look like WAWCD JSON
Normalizes WAWCD’s reciver-* typo fields to canonical receiver-* keys
Supports nested body objects in the payload
Preserves all other WAWCD fields unchanged
WAWCD Plugin Send Message
Send to one or many recipients (comma or newline separated)
Text messages with {first_name} placeholder support
Media URLs (images, documents, etc.) with optional caption
Audio URLs
Location pins (latitude / longitude)
Random delay range (minDelay / maxDelay in seconds)
Scheduled send via schedule-timestamp
Personalization fields: first_name, last_name
Built-in credential test (validates API reachability and token)
60 second request timeout; bearer tokens are never echoed in error messages
Usable as an AI tool in n8n agent workflows