Actions148
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Files Actions
- Team Actions
- Labels Actions
- Departments 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
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
Overview
This node interacts with the SparkBot WhatsApp API to manage chat contacts, specifically allowing users to unblock one or more WhatsApp contacts associated with a given WhatsApp number (device). It is useful in scenarios where certain contacts were previously blocked and need to be restored to normal communication status.
Practical examples include:
- Customer support teams unblocking customers who were mistakenly blocked.
- Marketing teams restoring communication with contacts after resolving issues.
- Automating contact management workflows that require toggling block/unblock states on WhatsApp contacts.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the contacts will be unblocked. |
| Contact Phone Numbers | One or more phone numbers (1 to 50) in international E164 format representing contacts to unblock. |
Output
The node outputs JSON data representing the result of the unblock operation for each contact. This typically includes confirmation of successful unblocking or error details if any contact could not be unblocked.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the SparkBot WhatsApp API.
- The node depends on the SparkBot WhatsApp API service being accessible.
- The "WhatsApp Number" must be valid and linked to the authenticated account.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp number/device ID can cause failures.
- Incorrectly formatted contact phone numbers (not in E164 format) may lead to errors.
- Exceeding the maximum allowed contacts (more than 50) will likely cause rejection.
- Network or authentication errors with the SparkBot API.
Error Messages:
- Errors related to invalid credentials usually indicate misconfigured or expired API keys.
- Validation errors on phone numbers suggest checking the format and ensuring country codes are included.
- Rate limiting or quota exceeded errors imply too many requests in a short time; consider adding delays or upgrading API plan.
Resolving these generally involves verifying input parameters, ensuring correct API key setup, and confirming network connectivity.
Links and References
- E.164 Phone Number Format
- SparkBot WhatsApp API documentation (refer to your provider's official docs for detailed API usage)