DinastiAPI Status icon

DinastiAPI Status

Send WhatsApp status messages using DinastiAPI API

Overview

This node allows users to send WhatsApp status messages through the DinastiAPI service. It supports sending different types of status content including text, images, videos, and audio. The node is useful for automating status updates on WhatsApp accounts, such as broadcasting announcements, sharing media content, or posting promotional material.

A practical example would be a marketing automation workflow that posts daily image statuses with captions to engage customers, or a support system that sends audio status updates with voice notes.

Properties

Name Meaning
Image Source Selects the source of the image:
- Binary Data (from previous node)
- Base64 encoded image
- URL to image file
Binary Property Name of the binary property containing the image when "Binary Data" is selected
Base64 Image Base64 encoded image string with data URL prefix (required if Base64 source is selected)
Image URL URL to the image file (required if URL source is selected)
Caption Optional caption text for the image status
Additional Options Collection of optional parameters:
- Message ID: Custom message identifier
- Audience: Comma-separated list of JIDs to specify who can see the status
- Exclude List: Comma-separated list of JIDs to exclude from viewing

Output

The node outputs JSON data representing the response from the DinastiAPI after attempting to send the image status. This typically includes confirmation details or error information related to the status update request.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the DinastiAPI service.
  • The node uses the DinastiAPI endpoint to send WhatsApp status messages.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Binary Property Not Found: If the selected binary property does not exist in the input data, the node throws an error stating Binary property "<propertyName>" not found. Ensure the previous node outputs binary data under the specified property name.
  • Invalid Base64 or URL Input: Providing malformed base64 strings or invalid URLs may cause the API request to fail. Verify the correctness of these inputs.
  • API Authentication Errors: If the API key credential is missing or invalid, requests will fail. Confirm the credential configuration.
  • Audience and Exclude List Formatting: These fields require comma-separated JIDs without extra spaces. Improper formatting might lead to unexpected behavior.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to allow workflow continuation despite individual item failures.

Links and References

Discussion