Overview
This node triggers workflows in n8n when specific WhatsApp call events occur. It listens for incoming webhook POST requests from a configured WhatsApp instance and activates the workflow if the event matches one of the selected call event types.
Common scenarios include:
- Automating responses or logging when an incoming WhatsApp call is received.
- Tracking call acceptance or rejection events to update CRM systems or notify teams.
- Integrating WhatsApp call activity into broader communication or support workflows.
For example, a user can configure this node to trigger when a call is received, then automatically send a follow-up message or create a support ticket.
Properties
| Name | Meaning |
|---|---|
| Remember to configure WhatsApp instance (session or server) to send events to Webhook URL | Informational notice reminding users to set up their WhatsApp instance to forward events to the webhook URL provided by this node. |
| Events | The WhatsApp call events to listen for. Options: "Call Received", "Call Accepted", "Call Rejected". Multiple selections allowed. |
Output
The node outputs JSON data representing the webhook payload received from the WhatsApp instance. Specifically, it returns an array with a single object containing the full body of the webhook request under the json output field.
Example output structure:
[
{
"event": "call.received",
"body": {
// Full webhook payload details sent by WhatsApp instance
}
}
]
No binary data output is produced by this node.
Dependencies
- Requires a WhatsApp instance (either session-based or server-based) properly configured to send call event webhooks to the URL exposed by this node.
- No additional external API keys or credentials are managed by this node itself; however, the WhatsApp instance setup must be done externally.
- The node expects to receive HTTP POST requests at the webhook path
/whatsapp-call.
Troubleshooting
- No triggers firing: Ensure that your WhatsApp instance is correctly configured to send call event webhooks to the exact webhook URL provided by this node.
- Selected events not triggering: Verify that the event type sent by the WhatsApp instance matches one of the selected events in the node’s configuration.
- Empty or unexpected payloads: Confirm that the WhatsApp instance sends the expected JSON structure and that the webhook endpoint is reachable.
- Webhook URL exposure: Make sure your n8n instance is accessible from the internet or via a tunnel so that WhatsApp can reach the webhook URL.