Actions21
Overview
The node "ZuckZapGo AI" enables sending various types of WhatsApp messages through the ZuckZapGo API, optimized for AI workflows. It supports a wide range of messaging operations including sending text, images, documents, audio, video, locations, contacts, stickers, interactive buttons, lists, polls, and links. Additionally, it can retrieve user info, group lists, newsletters, avatars, business profiles, and session status.
Specifically, the Send Audio operation allows sending audio messages either as voice notes (push-to-talk style) or as regular audio files in OGG Opus format. The audio content can be provided via binary data from previous nodes, base64-encoded strings, or URLs to audio files.
This node is beneficial for automating WhatsApp communications in customer support, marketing campaigns, notifications, or AI-driven chatbots that require multimedia messaging capabilities.
Practical Examples
- Sending a voice note audio message to a customer after an AI chatbot interaction.
- Broadcasting audio announcements to WhatsApp groups or newsletters.
- Sharing recorded audio instructions or podcasts via WhatsApp using URLs or embedded base64 audio.
Properties
| Name | Meaning |
|---|---|
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to which the message will be sent. |
| Audio Source | Method to provide the audio: Binary Data (from previous node), Base64 (base64 encoded audio string), or URL (link to audio file). |
| Binary Property | Name of the binary property containing the audio data when using Binary Data as source. Default is "data". |
| Base64 Audio | Base64 encoded audio string in opus format, required if Audio Source is set to Base64. |
| Audio URL | URL to the audio file, required if Audio Source is set to URL. |
| Voice Note (PTT) | Boolean flag indicating whether to send the audio as a voice note (push-to-talk style) or as a regular audio file. Defaults to true (voice note). |
| Additional Options | Collection of optional settings including: - Custom Message ID - Presence Simulation (typing/recording indicator duration) - Message Duration (disappearing message timer) - View Once (message view limit) - Context Information (for replies, forwards, mentions) |
Output
The node outputs JSON data representing the response from the ZuckZapGo API for the executed operation. For the Send Audio operation, this typically includes confirmation details about the sent message such as message ID, status, timestamps, and any metadata returned by the API.
If the operation involves retrieving avatars with the option to save as binary, the output may include binary data representing the avatar image.
No direct binary output is produced for sending audio; the audio content is sent as input, and the output is the API response metadata.
Dependencies
- Requires an active connection to the ZuckZapGo API service.
- Needs an API key credential configured in n8n for authentication with ZuckZapGo.
- Uses helper functions to prepare media data from binary buffers.
- Network access to URLs if audio is provided via URL.
- Properly formatted base64 audio strings if using base64 input.
Troubleshooting
- Binary Property Not Found: If the specified binary property for audio does not exist in the input data, the node throws an error like
Binary property "xyz" not found. Ensure the binary data exists and the property name matches exactly. - Invalid Audio Format: Audio must be in OGG Opus format when using base64 or binary sources. Using unsupported formats may cause failures.
- Missing Required Fields: The recipient phone number or audio source fields are mandatory. Omitting these will result in errors.
- Network Issues: When providing audio via URL, ensure the URL is accessible and returns the correct audio content.
- API Errors: The node passes through errors from the ZuckZapGo API. Common issues include invalid credentials, rate limits, or malformed requests.
- View Once Option: If enabled, the audio message can only be viewed once by the recipient. Use carefully depending on use case.
To resolve errors:
- Verify all required parameters are correctly set.
- Confirm binary data availability and correctness.
- Check network connectivity and URL validity.
- Review API credentials and permissions.
Links and References
- ZuckZapGo GitHub Repository – Official documentation and source code for the ZuckZapGo API.
- WhatsApp Multimedia Messaging Guidelines – Refer to WhatsApp's official docs for supported media formats and best practices.
- n8n Documentation – For configuring credentials and working with binary data in n8n workflows.