Actions21
Overview
The "Send Video" operation of the ZuckZapGo AI node enables sending video messages via WhatsApp using the ZuckZapGo API. It supports multiple video input formats including binary data from previous nodes, base64-encoded strings, or direct URLs to video files. Users can add captions and customize message options such as disappearing message duration, presence simulation (typing/recording indicators), view-once mode, and context information for replies, forwards, and mentions.
This node is beneficial in scenarios where automated workflows need to send rich media content like videos to WhatsApp users, groups, newsletters, or LIDs. For example, businesses can use it to send promotional videos, tutorials, or personalized video messages to customers directly through WhatsApp.
Properties
| Name | Meaning |
|---|---|
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to which the video will be sent. |
| Video Source | The source type of the video: • Binary Data - Use binary data from a previous node. • Base64 - Provide a base64 encoded video string. • URL - Provide a direct URL to the video file. |
| Binary Property | (If Video Source is Binary) The name of the binary property containing the video data. Default is "data". |
| Base64 Video | (If Video Source is Base64) The base64 encoded video string. Must be H.264 codec with AAC audio. |
| Video URL | (If Video Source is URL) The URL pointing to the video file. |
| Caption | Optional caption text to accompany the video message. |
| Additional Options | Collection of optional settings: • Message ID: Custom message identifier (auto-generated if omitted). • Presence Simulation: Simulate typing/recording indicator for specified milliseconds (0-30000 ms). • Message Duration: Set WhatsApp disappearing message duration (No expiration, 24 hours, 7 days, 90 days). • View Once: Whether the video can only be viewed once. • Context Information: Settings for replies, forwards, mentions including forwarded flag, mention all, specific mentioned users, participant JID, and reply message ID. |
Output
The node outputs a JSON object representing the response from the ZuckZapGo API after attempting to send the video message. This typically includes status information about the message delivery.
If the operation is used as a tool with response optimization enabled, the output may be truncated or structured to reduce noise for AI processing.
No binary data is output by this operation itself; it sends video data but does not return video content.
Dependencies
- Requires an active connection to the ZuckZapGo API service.
- Requires an API key credential configured in n8n for authentication with ZuckZapGo.
- The node uses helper functions to prepare media data buffers for transmission.
- Network access to URLs provided for video files is necessary if using URL as the video source.
Troubleshooting
- Binary Property Not Found: If the selected binary property does not exist in the input data, the node throws an error indicating the missing property. Ensure the binary data is correctly passed from previous nodes and the property name matches exactly.
- Invalid Video Format: Base64 video must be encoded with H.264 codec and AAC audio. Using unsupported formats may cause message sending failures.
- Invalid Recipient Format: The recipient must be a valid phone number or group/newsletter/LID ID with correct suffixes (@g.us, @newsletter, @lid). Incorrect formatting may result in errors.
- Network Issues: When using URL sources, ensure the URL is accessible and points to a valid video file.
- API Errors: Any errors returned by the ZuckZapGo API will be included in the node's output JSON under an error field if continueOnFail is enabled, otherwise they will cause the node to fail.
Links and References
- ZuckZapGo GitHub Repository – Official documentation and source code for the ZuckZapGo API.
- WhatsApp Media Guidelines – For supported video codecs and formats (H.264 video, AAC audio recommended).