Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node enables users to create and manage webhooks for WhatsApp events via the Wassenger API. Specifically, the "Create Webhook" operation allows setting up an HTTP endpoint that will receive notifications when certain WhatsApp-related events occur, such as new inbound or outbound messages, message updates, status changes, and more.
Common scenarios where this node is beneficial include:
- Automating workflows triggered by incoming WhatsApp messages.
- Tracking message delivery statuses or failures in real-time.
- Synchronizing WhatsApp contact or group updates with other systems.
- Monitoring session status or reacting to chat events programmatically.
For example, a user can create a webhook that listens for new inbound messages and automatically triggers a workflow to respond or log these messages in a CRM system.
Properties
| Name | Meaning |
|---|---|
| Webhook Name | Internal name for the webhook (max 30 characters). |
| Webhook URL | Publicly accessible endpoint URL that will receive HTTP POST requests when specified events occur. |
| Event Types | List of event types to be notified by this webhook. Options include: - New Inbound Message - New Outbound Message - Outbound Message Sent - Outbound Message Delivery Status - Outbound Message Failed - Message Updated - Message Reaction - Channel Message Received - Status Update - Group Update - Chat Update - Contact Update - WhatsApp Session Status |
| Device ID (Optional) | Restrict webhook notifications to a specific WhatsApp device identified by a 24-character hexadecimal ID. |
Output
The node outputs JSON data representing the response from the webhook creation API call. This typically includes details about the created webhook such as its identifier, configured events, target URL, and associated device if specified.
No binary data output is involved in this operation.
Dependencies
- Requires an active Wassenger API key credential configured in n8n to authenticate API requests.
- The webhook URL must be publicly accessible to receive HTTP POST callbacks from Wassenger.
- The node depends on the Wassenger WhatsApp API service to manage webhook registrations.
Troubleshooting
- Webhook URL unreachable: Ensure the provided webhook URL is publicly accessible and can accept POST requests. Use tools like
curlor online webhook testers to verify. - Invalid event types: Confirm that selected event types are valid and supported by the API.
- Device ID restrictions: If specifying a device ID, ensure it matches a valid registered WhatsApp device in your Wassenger account.
- API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Error responses from API: Check error messages returned in the node output JSON for clues; common issues include rate limits, invalid parameters, or network problems.
Links and References
- Wassenger API Documentation (for detailed webhook event types and API usage)
- n8n Webhook Node Documentation (general webhook handling concepts)