Wassenger Trigger
AI-generatedOverview
This node acts as a trigger for events occurring in the Wassenger WhatsApp automation platform. It listens for various WhatsApp-related webhook events such as incoming or outgoing messages, message status updates, group changes, contact updates, and more. When one of the subscribed events happens, the node activates the workflow with the event data.
Common scenarios where this node is beneficial include:
- Automating responses to new inbound WhatsApp messages.
- Tracking delivery and read statuses of outbound messages.
- Reacting to group membership changes or chat updates.
- Processing user status updates or contact information changes.
- Integrating WhatsApp channel messages into broader workflows.
For example, you could use this node to start a workflow that sends an automated reply when a new inbound text message arrives or to log message delivery failures for customer support follow-up.
Properties
| Name | Meaning |
|---|---|
| Webhook name | Internal name for the webhook (max 30 characters) used for your reference within n8n. |
| WhatsApp number | Optionally restrict events to a specific WhatsApp number/device. If left empty, listens to all. |
| Events | The types of WhatsApp events to subscribe to. Options include: |
| - New Inbound Message Received | |
| - New Outbound Message Delivered | |
| - Message Read or Played by User | |
| - Message Delivery Failed | |
| - Group Updated | |
| - Message Updated (Poll Votes, Meeting Events) | |
| - Message Reaction Added/Removed | |
| - New User Status Published | |
| - New Channel Message Received | |
| - Chat Updated (Assigned, Resolved, etc.) | |
| - WhatsApp Session Changes | |
| - Contact Information Updated | |
| Sample event to notify | Select a sample event matching your use case to test and configure the webhook JSON data structure. |
Output
The node outputs the webhook event payload as JSON data. The output contains the full event details received from Wassenger, which can include message content, sender info, timestamps, status updates, group changes, and other relevant metadata depending on the event type.
If the event includes media (images, audio, video, documents), the node outputs the associated metadata but does not directly output binary data. Handling of media files would require additional steps in the workflow.
The output JSON structure varies based on the event subscribed but generally follows Wassenger's webhook event schema.
Dependencies
- Requires an API key credential for authenticating with the Wassenger API.
- Needs internet access to register and receive webhook events from Wassenger.
- The node uses HTTP POST webhooks internally; ensure your n8n instance is accessible via a public URL or tunnel.
- Environment variable
N8N_RUNTIME_CLIENTinfluences some behavior related to device listing.
Troubleshooting
- No webhook URL available for registration: Ensure your n8n instance has a valid external URL configured so the webhook URL can be generated.
- At least one event must be selected: You must select one or more events to subscribe to; otherwise, webhook creation will fail.
- Webhook registration failed with status 409: This means a webhook with the same parameters already exists; usually safe to ignore.
- No WhatsApp numbers available: If no devices are connected or accessible, the device dropdown may show "invalid" or no options. Connect a WhatsApp number in Wassenger or upgrade your plan.
- Webhook deletion errors: Usually safe to ignore if the webhook was already deleted or not found.
- API errors: Check your API key credential validity and network connectivity.
Links and References
- Wassenger API Documentation
- n8n Webhook Documentation
- WhatsApp Business API Concepts (for understanding WhatsApp event types)