ZuckZapGo Chat icon

ZuckZapGo Chat

Perform chat operations with ZuckZapGo WhatsApp API

Actions6

Overview

The node "ZuckZapGo Chat" enables interaction with the ZuckZapGo WhatsApp API to perform various chat-related operations. Specifically, the Download Media operation allows users to download different types of media (image, video, audio, document) from WhatsApp messages by providing necessary metadata and encryption keys.

This node is beneficial in scenarios where automated workflows need to retrieve and process media content shared over WhatsApp, such as archiving images, analyzing audio messages, or storing documents for further processing.

Practical example:
A user can configure this node to download an image sent in a WhatsApp message by specifying the media URL, encryption key, MIME type, and file hash details. The downloaded media is then available as binary data within the workflow for saving to disk, uploading to cloud storage, or further manipulation.

Properties

Name Meaning
Media Type Type of media to download. Options: Audio, Document, Image, Video
Media URL URL of the media file to download (required)
Direct Path Optional direct path to the media file
Media Key Encryption key for the media (required)
Mime Type MIME type of the media file (e.g., image/jpeg) (required)
File SHA256 SHA256 hash of the file (required)
File Length Size of the file in bytes (required)
Additional Fields Collection of optional fields:
- File Enc SHA256: Encrypted file SHA256 hash
- Binary Property Name: Name of the binary property to store the downloaded media (default: "data")

Output

  • The node outputs the downloaded media as binary data attached to the item under a binary property.
  • By default, the binary property name is "data", but it can be customized via the "Binary Property Name" additional field.
  • The binary data includes:
    • data: Base64 encoded media content
    • mimeType: MIME type of the media (e.g., image/jpeg)
    • fileExtension: File extension inferred from the MIME type (e.g., jpg, mp4, ogg, pdf)
    • fileName: A generated filename like downloaded-media.jpg

This structure allows downstream nodes to easily access and manipulate the media file.

Dependencies

  • Requires connection to the ZuckZapGo WhatsApp API using an API key credential configured in n8n.
  • The node uses an internal helper function to make authenticated POST requests to specific API endpoints depending on the media type.
  • Proper configuration of the API credential and network access to the ZuckZapGo service is necessary.

Troubleshooting

  • Common issues:

    • Incorrect or missing media encryption key (mediaKey) will cause decryption failures.
    • Invalid or expired media URLs may result in failed downloads.
    • Mismatched SHA256 hashes or file length values could indicate corrupted or tampered files.
    • Missing required properties like MIME type or file SHA256 will prevent the operation.

  • Error messages:

    • Errors returned from the API request will be surfaced as error messages in the node output.
    • If "Continue On Fail" is enabled, errors for individual items will be included in the output JSON with an error field describing the issue.

  • Resolution tips:

    • Verify all required input parameters are correctly set.
    • Ensure the media URL is accessible and valid.
    • Confirm the encryption key matches the media file.
    • Check API credentials and connectivity to the ZuckZapGo service.

Links and References

Discussion