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 interacts with the Wassenger WhatsApp API to manage chat contacts, specifically allowing users to unblock one or more WhatsApp contacts associated with a given WhatsApp number. It is useful in scenarios where contacts were previously blocked and need to be restored for communication.
For example, a business using WhatsApp for customer support might block spammy or abusive contacts temporarily and later decide to unblock them to resume conversations. This node automates that unblocking process by specifying the WhatsApp number (device) and the list of contact phone numbers to unblock.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which contacts will be unblocked. |
| Contact Phone Numbers | One or more phone numbers (1 to 50) in international E164 format to be unblocked from the device. |
Output
The node outputs JSON data representing the result of the unblock operation for each input item. Each output JSON object contains the response from the Wassenger API related to the unblock action on the specified contacts.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger API service being accessible and properly configured.
- The "WhatsApp Number" must correspond to a valid registered device within the Wassenger system.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp number (device ID) may cause the API call to fail.
- Providing phone numbers not in E164 format or exceeding the maximum allowed count (50) can lead to errors.
- Network or authentication failures if the API key is invalid or the Wassenger service is unreachable.
Error messages:
- Errors returned from the API typically include descriptive messages about invalid parameters or authorization failures.
- If the node throws an error about missing credentials, ensure the API key is set up correctly in n8n.
- To resolve contact format errors, verify all phone numbers include the country code prefix and are formatted according to E164 standards.