Zender icon

Zender

Interact with Zender WhatsApp API

Overview

The node enables sending SMS messages via the Zender API, supporting both single and bulk SMS sending modes. It allows users to send messages either through linked devices or by using credits via a gateway. This node is useful for automating SMS notifications, marketing campaigns, alerts, or any scenario requiring programmatic SMS delivery.

For the Send SMS operation, it sends a single SMS message to a specified recipient phone number with customizable options such as SIM slot selection, priority, and link shortening.

Practical examples:

  • Sending an appointment reminder SMS to a customer.
  • Sending a verification code or alert message to a user’s mobile phone.
  • Sending transactional SMS from an automated workflow.

Properties

Name Meaning
Mode SMS sending mode: either "Devices" (sending via linked devices) or "Credits" (sending via gateway credits).
Phone Number Recipient mobile number to which the SMS will be sent.
Message The text content of the SMS message. Supports spintax formatting for dynamic content.
SIM Slot SIM card slot number to use when sending via devices mode. Options: SIM 1 or SIM 2.
Additional Fields Collection of optional fields:
- Device ID Unique ID of the linked device used for sending (required if mode is Devices).
- Gateway Partner device or gateway ID used for sending (required if mode is Credits).
- Priority Message priority in devices mode: High Priority or Normal Priority.
- Shortener ID Optional numeric 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 SMS. This typically includes status information about the message submission, such as success confirmation, message IDs, or error details.

No binary data output is produced by this operation.

Example output JSON structure (simplified):

{
  "status": "success",
  "messageId": "1234567890",
  "details": "Message queued for sending"
}

Dependencies

  • Requires an API key credential for authenticating with the Zender API.
  • The base URL and secret API key must be configured in the node credentials.
  • The node uses HTTP POST requests with URL-encoded form data to communicate with the Zender SMS endpoints.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrect phone number format may result in message rejection.
    • Using device mode without specifying a valid linked device ID will fail.
    • Gateway ID required when using credits mode; omission leads to errors.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Authentication errors: Verify that the API key credential is correctly set up.
    • Validation errors on phone numbers or parameters: Ensure phone numbers are in correct format and all required fields are provided.
    • API rate limits or quota exceeded: Check your Zender account limits and usage.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error messages per item.

Links and References

  • Zender API Documentation (for detailed API endpoint info)
  • n8n documentation on HTTP Request Node (for understanding underlying HTTP calls)
  • SMS sending best practices and phone number formatting guidelines (e.g., E.164 format)

Discussion