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 integrates with the Wassenger WhatsApp API to manage WhatsApp numbers. Specifically, the Create Number operation allows users to add a new WhatsApp number to their Wassenger account by specifying an alias and subscription plan, along with optional details such as description, agent access, and payment intent.
Common scenarios for this node include:
- Automating the onboarding of new WhatsApp numbers into a business's messaging platform.
- Managing multiple WhatsApp numbers programmatically for different departments or campaigns.
- Assigning shared chat access to agents on platform plans to facilitate team collaboration.
Practical example:
- A customer support team wants to add a new WhatsApp number with a "Business" billing plan and assign several agents to handle incoming chats through that number. This node can automate that process within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Alias | Alias or name for the WhatsApp number (2-30 characters). |
| Billing Plan | Subscription plan for the WhatsApp number. Options: Professional, Business, Enterprise, Gateway Professional, Gateway Business, Gateway Enterprise, Platform Professional, Platform Business, Platform Enterprise. |
| Additional Options | Optional additional settings: |
| - Description | Description for the WhatsApp number (max 80 characters). |
| - Agent IDs | List of agent IDs to provide shared chat access (only applicable for Platform plans). |
| - Payment Intent | Payment intent ID string (starts with "pi_"), likely related to payment processing or invoicing. |
Output
The node outputs JSON data representing the newly created WhatsApp number resource as returned by the Wassenger API. This typically includes details such as the assigned number ID, alias, billing plan, status, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured with the user's account.
- No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
Common issues:
- Invalid or missing alias: Ensure the alias is between 2 and 30 characters.
- Unsupported billing plan: Select one of the predefined billing plan options.
- Agent IDs provided for non-platform plans: Agent assignment only works with platform billing plans.
- Invalid payment intent ID format: Should start with "pi_".
Error messages:
- Authentication errors: Verify the API key credential is valid and has necessary permissions.
- Validation errors from the API: Check input property values for correctness and completeness.
- Network or connectivity issues: Confirm network access to the Wassenger API endpoint.
Resolving these usually involves verifying input parameters, ensuring correct credential setup, and checking network connectivity.
Links and References
- Wassenger Official Website
- Wassenger API Documentation (for detailed API usage and billing plans)
- n8n Documentation on Creating Custom Nodes