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 status into broader communication or support workflows.
For example, you could use this node to trigger a workflow that logs every incoming WhatsApp call or sends a notification when a call is accepted.
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". You can select multiple events to trigger on. |
Output
The node outputs JSON data representing the webhook payload received from the WhatsApp instance. The output structure includes all details sent in the webhook body under a body field.
Example output JSON structure:
{
"body": {
"event": "call.received",
// ... other event-specific data fields
}
}
No binary data is output by this node.
Dependencies
- Requires a WhatsApp instance (either session-based or server) configured to send call event webhooks to the URL exposed by this node.
- No additional API keys or credentials are handled directly by this node; it relies on external WhatsApp infrastructure to push events.
Troubleshooting
- No workflow trigger despite calls happening: Ensure your WhatsApp instance is correctly configured to send webhook events to the node’s webhook URL.
- Workflow triggers but no data: Verify that the selected events in the node settings match the actual event types sent by your WhatsApp instance.
- Error or empty response: Check that the webhook HTTP method is POST and that the payload contains an
eventfield. - Multiple events not triggering: Confirm that the node’s "Events" property includes all desired event types.