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 "Update Number" operation for the WhatsApp Numbers resource allows users to modify the configuration and metadata of a specific WhatsApp number managed via the Wassenger API. This node is useful when you want to change settings such as enabling or disabling the number, updating its alias or description, changing billing plans, adjusting webhook notifications, or modifying policies related to reboot, data retention, and message delivery speed.
Practical examples include:
- Disabling a WhatsApp number temporarily without deleting it.
- Changing the alias or description to better identify the number in your system.
- Switching the billing plan to upgrade or downgrade service levels.
- Restricting webhook notifications to certain endpoints for targeted event handling.
- Adjusting the device session reboot policy to control automatic restarts.
- Setting data retention policies to comply with privacy or storage requirements.
- Controlling the maximum message delivery speed to manage throughput and avoid rate limits.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number ID | The unique identifier of the WhatsApp number to update. |
| Enable | Boolean flag to enable (true) or disable (false) the WhatsApp number. |
| Alias | New alias or name for the WhatsApp number (between 2 and 30 characters). |
| Description | New description for the WhatsApp number (up to 80 characters). |
| Billing Plan | Select a new billing plan for the number. Options: Professional, Business, Enterprise, Gateway Professional, Gateway Business, Gateway Enterprise, Platform Professional, Platform Business, Platform Enterprise. Charges may apply. |
| Webhook IDs | List of webhook endpoint IDs to restrict notifications to these endpoints only. |
| Reboot Policy | Device session reboot policy controlling automatic restarts. Options range from Disabled to 18 Hours intervals (e.g., 10 Minutes, 1 Hour, etc.). |
| Retention Policy | Data retention policy specifying how long data is kept. Options include Plan Defaults, Never, 5 Minutes up to 10 Days. |
| Delivery Speed | Maximum message delivery speed per minute. Options range from Plan Default to 150 messages per minute. |
Output
The node outputs a JSON object representing the updated WhatsApp number's details after applying the changes. This typically includes confirmation of the updated fields and current status of the number.
If any error occurs during the update, and if the node is configured to continue on failure, the output will contain an error field with the error message.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Wassenger WhatsApp API.
- An API key credential must be configured in n8n to authenticate requests.
- Proper permissions on the Wassenger account to update WhatsApp numbers.
- The node relies on internal methods that interact with the Wassenger API endpoints for numbers management.
Troubleshooting
Common Issues:
- Invalid or missing WhatsApp Number ID will cause the update to fail.
- Providing invalid values for fields like alias length or unsupported billing plans can result in errors.
- Insufficient permissions or expired API keys will prevent successful updates.
- Network connectivity issues may cause timeouts or failures.
Error Messages:
"WhatsApp Number ID is required": Ensure the ID is provided and valid."Invalid billing plan": Choose one of the supported billing plan options."Unauthorized"or"Authentication failed": Verify the API key credential is correct and active."Rate limit exceeded": Reduce the delivery speed or check API usage limits.
Resolution Tips:
- Double-check all input parameters for correctness.
- Confirm API credentials and permissions.
- Use smaller batch sizes or slower delivery speeds if hitting rate limits.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.