WAHA WhatsApp Call Trigger
AI-generatedOverview
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 where this node is beneficial 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, a user can configure this node to trigger when a call is received, then automatically send a notification to a support team or log the call details in a database.
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 send events to the webhook URL provided by this node. |
| Events | The WhatsApp call events to listen for. Options: "Call Received" (incoming call received), "Call Accepted" (call accepted), "Call Rejected" (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 body property.
Example output JSON structure:
[
{
"body": {
"event": "call.received",
"otherEventData": "..."
}
}
]
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 handled directly by this node; authentication and setup must be managed on the WhatsApp instance side.
- The node expects to receive HTTP POST requests at the webhook path
/whatsapp-call.
Troubleshooting
- Webhook not triggering: Ensure that the WhatsApp instance is correctly configured to send call event webhooks to the exact URL provided by this node. Verify network accessibility and that the workflow is active.
- No data received despite calls happening: Confirm that the selected events in the node’s properties match the actual events sent by the WhatsApp instance.
- Empty output: If the event received is not included in the selected events list, the node will not emit any data.
- Incorrect webhook path: Make sure the webhook path
/whatsapp-callis not changed or blocked by firewalls or proxies.