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
The node interacts with the Wassenger WhatsApp API to manage message queues for WhatsApp numbers. Specifically, the "Set Queue Status" operation allows users to control how messages are processed in the queue of a selected WhatsApp number. This is useful in scenarios where you want to temporarily pause message delivery, reject new incoming messages, or freeze the queue entirely, for example during maintenance or high load periods.
Practical examples:
- Pausing message delivery while performing system updates but still accepting new messages.
- Rejecting new messages but allowing existing queued messages to be delivered, useful when limiting new traffic but clearing backlog.
- Freezing the queue to stop all message processing and rejecting new messages, e.g., during critical outages.
- Forcing immediate delivery of all queued messages for 30 minutes when switching back to active status.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number whose message queue status you want to set. |
| Status | The desired queue processing status: - Active: Deliver messages and accept new ones. - Pause: Do not deliver messages but accept new ones. - Reject: Deliver existing messages but reject new ones. - Freeze: Do not deliver messages and reject new ones. |
| Force Delivery | Boolean flag to force delivery of all queued messages immediately for 30 minutes. Only works if status is "active" or "reject". |
Output
The node outputs JSON data representing the result of setting the queue status for the specified WhatsApp number. The exact structure depends on the API response from Wassenger but generally includes confirmation of the updated status and any relevant metadata about the queue state.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node relies on the Wassenger service being accessible and properly configured.
- The "WhatsApp Number" options are dynamically loaded via a method that fetches available devices/numbers from Wassenger.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number ID will cause errors; ensure the device ID is correct.
- Using "Force Delivery" with unsupported statuses (other than "active" or "reject") will have no effect.
- Network or authentication failures with the Wassenger API can cause execution errors.
Error messages:
- Authentication errors indicate invalid or missing API credentials; verify and update your API key.
- Validation errors may occur if required parameters are missing or invalid; double-check input properties.
- API rate limits or service downtime may cause temporary failures; retry after some time.
Links and References
- Wassenger Official Website
- Wassenger API Documentation (for detailed API endpoints and queue management)
- n8n documentation on Creating Custom Nodes