Overview
This node allows sending various types of WhatsApp messages through the DinastiAPI WhatsApp API. It supports a wide range of message formats including text, images, audio, video, documents, stickers, locations, contacts, templates with buttons, interactive buttons, lists, polls (for groups), and links with automatic previews.
Common scenarios where this node is beneficial include automating customer support responses, broadcasting multimedia content, conducting polls in group chats, sharing contact cards or locations, and sending interactive messages with buttons or lists to engage users.
For example:
- Sending a promotional image with a caption to a customer.
- Sharing a location pin for an event.
- Sending a poll to a group chat to gather opinions.
- Delivering a document such as a PDF invoice.
- Sending a template message with quick reply buttons for easy user interaction.
Properties
| Name | Meaning |
|---|---|
| Message Type | Type of message to send. Options: Text, Image, Audio, Video, Document, Sticker, Location, Contact, Template, Buttons, List, Poll, Link. |
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) identifying the message recipient. |
| Message | Text content of the message (for Text and Buttons message types). |
| Link URL | URL to send with automatic preview generation (for Link message type). |
| Caption | Optional text accompanying the link (for Link message type). |
| Image Source | Source of the image: Binary data from previous node, Base64 encoded string, or URL (for Image message type). |
| Binary Property | Name of the binary property containing the image (when using Binary Data source for Image). |
| Base64 Image | Base64 encoded image string with data URL prefix (for Image with Base64 source). |
| Image URL | URL to the image file (for Image with URL source). |
| Caption | Caption text for the image (for Image and Video message types). |
| Audio Source | Source of the audio: Binary data, Base64 encoded string, or URL (for Audio message type). |
| Binary Property | Name of the binary property containing the audio (when using Binary Data source for Audio). |
| Base64 Audio | Base64 encoded audio in opus format (for Audio with Base64 source). |
| Audio URL | URL to the audio file (for Audio with URL source). |
| Video Source | Source of the video: Binary data, Base64 encoded string, or URL (for Video message type). |
| Binary Property | Name of the binary property containing the video (when using Binary Data source for Video). |
| Base64 Video | Base64 encoded video (H.264 codec, AAC audio) (for Video with Base64 source). |
| Video URL | URL to the video file (for Video with URL source). |
| Document Source | Source of the document: Binary data, Base64 encoded string, or URL (for Document message type). |
| Binary Property | Name of the binary property containing the document (when using Binary Data source for Document). |
| Base64 Document | Base64 encoded document (for Document with Base64 source). |
| Document URL | URL to the document file (for Document with URL source). |
| File Name | Name of the document file (required for Document message type). |
| Sticker Source | Source of the sticker: Binary data, Base64 encoded string, or URL (for Sticker message type). |
| Binary Property | Name of the binary property containing the sticker (when using Binary Data source for Sticker). |
| Base64 Sticker | Base64 encoded sticker in WebP format (for Sticker with Base64 source). |
| Sticker URL | URL to the sticker file (for Sticker with URL source). |
| Latitude | Latitude coordinate (for Location message type). |
| Longitude | Longitude coordinate (for Location message type). |
| Location Name | Name of the location (optional for Location message type). |
| Contact Name | Full name of the contact (for Contact message type). |
| VCard | VCard data string representing the contact card (for Contact message type). |
| Content | Main content of the template message (for Template message type). |
| Footer | Footer text for the template message (optional). |
| Buttons | Collection of buttons to add to the template message. Each button has display text and type (Quick Reply, URL, Call). |
| Button Text | Text for the list button (for List message type). |
| Description | Description of the list (for List message type). |
| Top Text | Header text shown above the list (for List message type). |
| Footer Text | Text shown below the list (optional for List message type). |
| List Items | Collection of items in the list. Each item includes Title, Description, and Row ID (unique identifier). |
| Poll Question | Question text for the poll (groups only) (for Poll message type). |
| Poll Options | Comma-separated list of poll options (for Poll message type). |
| Additional Options | Collection of optional settings: - Message ID (custom or auto-generated) - Presence Simulation (milliseconds to simulate typing or recording, max 30000ms) - Message Duration (expiration time) - View Once (only for image/video/audio) - Link Preview (enable automatic preview for URLs in text) - Context Information (reply, forward, mentions) |
Output
The node outputs JSON data representing the response from the DinastiAPI after sending the message. The output includes metadata about the sent message and any relevant status or error information.
If the message involves media (image, audio, video, document, sticker), the node handles binary data input but outputs only JSON metadata about the operation; it does not output binary data itself.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI WhatsApp API.
- The node uses the DinastiAPI endpoints to send messages via HTTP POST requests.
- No additional external dependencies are required beyond the configured API credentials.
Troubleshooting
- Binary Property Not Found: If you select a binary data source for media but the specified binary property does not exist in the input data, the node will throw an error like
Binary property "data" not found. Ensure that the previous node outputs binary data under the correct property name. - Invalid Recipient Format: The recipient must be a valid phone number or group/newsletter/LID identifier. Incorrect formatting may cause message sending failures.
- Message Type Mismatch: Providing properties incompatible with the selected message type (e.g., missing required fields) can cause errors.
- Presence Simulation Limits: The presence simulation delay must be between 0 and 30000 milliseconds; values outside this range are ignored.
- Message Duration Values: Only specific expiration durations are accepted (No Expiration, 24 Hours, 7 Days, 90 Days).
- Context Information: When replying to a message, both the message ID and participant JID must be provided to correctly reference the original message.
- Network or API Errors: Failures in connecting to the DinastiAPI service or invalid API credentials will result in errors. Verify API key validity and network connectivity.
Links and References
- DinastiAPI WhatsApp API Documentation (example placeholder, replace with actual)
- WhatsApp Business API Concepts
- n8n Documentation on Creating Custom Nodes