Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
The node enables sending bulk SMS messages through the Zender API. It supports two SMS sending modes: via linked devices or using credits through a gateway. Users can specify message content, campaign name, recipient phone numbers, contact groups, and additional options like SIM slot, priority, and link shortener ID.
This node is beneficial for marketing campaigns, notifications, alerts, or any scenario requiring mass SMS distribution with flexible targeting (individual numbers or groups) and control over sending mode and priority.
Example use case:
A marketing team wants to send a promotional SMS to thousands of customers grouped by region. They create a campaign, select the "Send Bulk SMS" operation, specify the campaign name, message content, and target groups, then execute the node to dispatch the messages efficiently.
Properties
| Name | Meaning |
|---|---|
| Mode | SMS sending mode; choose between "Devices" (sending via linked devices) or "Credits" (sending via partner gateway). |
| Message | The SMS message text to send. Supports spintax for dynamic content variations. |
| Campaign Name | Name of the SMS campaign (required for bulk SMS sending). |
| SIM Slot | SIM card slot number to use when sending via devices mode; options are SIM 1 or SIM 2. |
| Additional Fields | Collection of optional fields: |
| - Phone Numbers | Comma-separated list of recipient phone numbers (for bulk SMS). |
| - Groups | Comma-separated list of contact group IDs to target (for bulk SMS). |
| - Device ID | Unique identifier of the linked device used for sending (devices mode only). |
| - Gateway | Partner device or gateway ID used for sending (credits mode only). |
| - Priority | Message priority level in devices mode; options are High Priority or Normal Priority. |
| - Shortener ID | Optional ID for URL shortening within the message. |
Output
The node outputs JSON data representing the response from the Zender API after attempting to send the bulk SMS messages. This typically includes status information about the request, such as success confirmation, message IDs, or error details if the request failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Zender API.
- The node makes HTTP POST requests to Zender endpoints for sending SMS.
- Proper configuration of linked devices or gateways on the Zender platform is necessary depending on the chosen SMS sending mode.
- Network access to the Zender API base URL must be available.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect device ID or gateway ID may result in message sending errors.
- Improperly formatted phone numbers or empty recipient lists will cause the API to reject the request.
- Exceeding rate limits or quota restrictions on the Zender account can block message sending.
Error messages:
- Authentication errors: Verify that the API key credential is correctly set up and has required permissions.
- Validation errors: Check that all required parameters (campaign name, message, recipients) are provided and correctly formatted.
- Device/gateway errors: Confirm that the specified device or gateway exists and is active on the Zender platform.
- Network errors: Ensure stable internet connection and that the Zender API endpoint is reachable.
Links and References
- Zender API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- Best practices for SMS campaigns and compliance guidelines (varies by region)