WAWCD WhatsApp Receice Message
AI-generatedSummary
Receives WAWCD outgoing POST webhooks and starts the workflow with a normalized JSON payload. Configure the webhook URL in WAWCD; optionally require a shared token and reject payloads that lack recognizable WAWCD fields.
Inputs
- Path — Optional webhook path segment; if empty, n8n uses the generated webhook ID.
- Incoming Authentication — Defaults to None. Choose Shared Secret to check each request for the configured token in an Authorization: Bearer header or X-WAWCD-Token header.
- Webhook Token — Shown when Shared Secret is selected. Must match the WAWCD outgoing bearer token; a missing or incorrect token is rejected with HTTP 401.
- Strict Payload Validation — Defaults to false. When enabled, rejects JSON objects without user-whatsapp-number or recognized receiver-/reciver- fields with HTTP 400.
Output shape
One workflow item containing the webhook JSON as its json object.
Accepts a JSON object, including one nested in a body object. Normalizes reciver-* misspellings to receiver-* and flattens nested body fields; other fields are preserved. Successful requests receive {"ok":true}; invalid JSON or rejected payloads return HTTP 400, and failed authentication returns HTTP 401.