Actions37
- Instance Actions
- Message Actions
- Group Actions
- Contact Actions
- Chat Actions
- Campaign Actions
- Chatbot Actions
Overview
The node integrates with the UazAPI service, providing automation capabilities for WhatsApp through over 90 endpoints. Specifically, the Campaign - Create Advanced operation allows users to create advanced mass messaging campaigns with customizable sending delays to avoid spam detection or bans.
This operation is useful when you want to send personalized or bulk WhatsApp messages in a controlled manner, spacing out message sends randomly between a minimum and maximum delay. For example, marketing teams can use this to run promotional campaigns without triggering anti-spam mechanisms on WhatsApp.
Properties
| Name | Meaning |
|---|---|
| Delay Min (seconds) | Minimum delay in seconds between sending each message in the campaign (anti-ban measure). |
| Delay Max (seconds) | Maximum delay in seconds between sending each message in the campaign (anti-ban measure). |
These properties control the random delay interval between individual message sends within the campaign to reduce the risk of being flagged as spam.
Output
The output of the node is an array of JSON objects, each representing the response from the UazAPI after attempting to create the advanced campaign. The exact structure depends on the API response but generally includes details about the created campaign such as its ID, status, and any error messages if applicable.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the UazAPI service.
- Requires valid credentials containing at least the base URL and authentication tokens for UazAPI.
- The node uses HTTP requests authenticated via these credentials to communicate with the UazAPI endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing delayMin greater than delayMax may cause unexpected behavior.
- Network connectivity issues can prevent successful API calls.
- Improperly formatted phone numbers or campaign parameters might lead to API errors.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Validation errors from the API may indicate missing required fields or invalid values; check input parameters carefully.
- Rate limiting or ban-related errors suggest that delays between messages are too short; increase delayMin and delayMax values.
Links and References
- UazAPI Official Documentation (example placeholder link)
- WhatsApp Business API guidelines on message sending limits and best practices
- n8n documentation on creating custom nodes and using HTTP request helpers