ZuckZapGo AI icon

ZuckZapGo AI

Send WhatsApp messages using ZuckZapGo - optimized for AI workflows
Join our community

Actions21

Overview

The "Send Image" operation of the ZuckZapGo AI node enables sending image messages via WhatsApp using the ZuckZapGo API. It supports multiple image input formats including binary data from previous nodes, base64-encoded images, or direct URLs to image files. Users can add optional captions and advanced message context such as replies, forwards, mentions, and disappearing message settings.

This node is beneficial in scenarios where automated workflows need to send rich media content on WhatsApp, such as customer support bots sharing product images, marketing campaigns broadcasting promotional visuals, or AI assistants delivering visual information dynamically.

Practical examples:

  • Sending a product photo with a caption to a customer after an order confirmation.
  • Broadcasting event flyers to WhatsApp groups or newsletters.
  • Replying to user queries with relevant images fetched or generated dynamically.

Properties

Name Meaning
Recipient Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) identifying the message recipient.
Image Source Method to provide the image:
- Binary Data: Use binary data from a previous node.
- Base64: Provide a base64 encoded image string.
- URL: Provide a direct URL to the image file.
Binary Property (If Image Source is Binary Data) The name of the binary property containing the image data.
Base64 Image (If Image Source is Base64) Base64 encoded image string including the data URL prefix (e.g., data:image/jpeg;base64,...).
Image URL (If Image Source is URL) Direct URL to the image file to be sent.
Caption Optional text caption to accompany the image message.
Additional Options Collection of optional parameters:
- Message ID: Custom message identifier (auto-generated if omitted).
- Presence Simulation: Simulate typing/recording indicator for specified milliseconds.
- Message Duration: Set disappearing message duration (No expiration, 24 hours, 7 days, 90 days).
- View Once: Whether the message can only be viewed once.
- Context Information: Settings for replies, forwards, mentions (including forward flag, mention all, specific mentioned users, reply to message ID, participant).

Output

The node outputs JSON data representing the response from the ZuckZapGo API after attempting to send the image message. This includes status information about the message delivery and any metadata returned by the API.

If the "Save as Binary" option were applicable here (it is not for Send Image but for Get Avatar), binary data output would be summarized accordingly. For Send Image, the output is purely JSON indicating success or failure details.

Dependencies

  • Requires an active connection to the ZuckZapGo API service.
  • Requires configuration of an API key credential for authentication with ZuckZapGo.
  • The node uses internal helper functions to prepare media data and make HTTP requests to the API.
  • 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 like Binary property "X" not found. Ensure that the previous node outputs binary data under the specified property name.
  • Invalid Image Source: Providing an empty or invalid base64 string or URL will cause the API request to fail. Validate inputs before execution.
  • Recipient Format Errors: The recipient must be a valid phone number or group/newsletter/LID identifier. Incorrect formatting may lead to message delivery failure.
  • API Request Failures: Network issues or invalid API credentials will result in errors. Verify API key validity and network connectivity.
  • Context Information Misconfiguration: Improperly formatted context info (e.g., missing participant for replies) may cause errors or unexpected behavior.

To resolve these issues:

  • Double-check input property names and values.
  • Confirm the format of phone numbers and IDs.
  • Ensure the API key credential is correctly set up.
  • Review the API documentation for limits and requirements.

Links and References

  • ZuckZapGo GitHub Repository — Official source and documentation for the ZuckZapGo API.
  • WhatsApp Business API documentation (general concepts related to media messaging).
  • n8n documentation on handling binary data and custom node development.

Discussion