Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

This node enables sending WhatsApp messages via the Zender WhatsApp API. It supports sending different types of messages including text, media (images, audio, video), and documents. Users can specify recipients by phone number or group address and customize message priority and link shortening.

Common scenarios where this node is beneficial include:

  • Automating customer notifications or alerts through WhatsApp.
  • Sending multimedia content such as images, videos, or audio clips to customers.
  • Distributing documents like PDFs or Excel files directly via WhatsApp.
  • Running marketing campaigns with bulk messaging capabilities.

Practical example:

  • A business wants to send a promotional image with a caption to a list of customers on WhatsApp. They can use this node to specify the recipient numbers, upload the image either via URL or binary data, add a caption, and set the message priority for immediate delivery.

Properties

Name Meaning
Recipient Recipient phone number in E.164 format (e.g., +923012345678) or a group address to which the message will be sent.
Message Type Type of message to send. Options: Text, Media, Document.
Message Text content of the message or caption for media/document messages. Supports Spintax formatting for dynamic text variations.
Additional Fields Optional extra settings:
- Priority: Message priority with options High (Send Immediately) or Normal.
- Shortener ID: Numeric ID for link shortening (optional).
Media Source For media messages only. Source of the media file: URL or Binary File.
Media URL Direct URL to the media file (jpg, png, gif, mp4, mp3, ogg). Required if Media Source is URL.
Media Type Type of media being sent. Options: Image, Audio, Video. Required if Media Source is URL.
Binary Property Name of the binary property containing the media file. Required if Media Source is Binary File.
Document Source For document messages only. Source of the document file: URL or Binary File.
Document URL Direct URL to the document file. Required if Document Source is URL.
Document Name Filename with extension for the document (e.g., document.pdf). Required if Document Source is URL.
Document Type Type of document being sent. Options: PDF, XML, Excel (XLS), Excel (XLSX), Word (DOC), Word (DOCX). Required if Document Source is URL.
Binary Property Name of the binary property containing the document file. Required if Document Source is Binary File.
Account ID Unique identifier of the Zender WhatsApp account used to send the message. This is required to authenticate and route the message correctly.

Output

The node outputs JSON objects representing the response from the Zender WhatsApp API after attempting to send the message. The structure typically includes status information about the message delivery request.

If sending media or document files via binary data, the node handles multipart form-data uploads transparently but does not output binary data itself.

Example output JSON might contain fields such as:

  • Confirmation of message acceptance.
  • Message ID or tracking information.
  • Error details if the message failed to send.

Dependencies

  • Requires an active Zender WhatsApp API account with valid API credentials (an API secret key).
  • The node uses HTTP requests to communicate with the Zender API endpoints.
  • For sending media or documents as binary files, the node depends on the presence of binary data in the input items.
  • Proper configuration of the "Account ID" parameter is necessary to identify the WhatsApp account used for sending.

Troubleshooting

  • Invalid Recipient Format: Ensure the recipient phone number is in E.164 format (e.g., +1234567890). Incorrect formats may cause message sending failures.
  • Missing Account ID: The Account ID must be provided; otherwise, the API will reject the request.
  • Unsupported Media Types: When sending media or documents, ensure the file type matches the selected media/document type.
  • Binary Data Not Found: If using binary source for media or documents, verify that the specified binary property exists and contains valid data.
  • API Authentication Errors: Check that the API secret credential is correct and has sufficient permissions.
  • Message Priority Misconfiguration: Priority values should be either 1 (high) or 2 (normal); invalid values may cause unexpected behavior.
  • Link Shortener Issues: If using a shortener ID, confirm it is valid and configured in the Zender system.

Common error messages returned by the API are passed through the node's output. Review these messages for specific issues such as authentication failure, invalid parameters, or quota limits.

Links and References

Discussion