Actions21
Overview
This node enables sending WhatsApp messages using the ZuckZapGo API, optimized for AI workflows. It supports a wide range of message types including text, images, documents, audio, video, locations, contacts, stickers, interactive buttons, lists, polls, and links. The "Send Sticker" operation specifically allows sending animated or static stickers in WebP format to individual users, groups, newsletters, or LIDs.
Common scenarios include automating customer support chats, broadcasting updates with rich media, engaging users with interactive content, and integrating AI-driven messaging workflows that require sending expressive stickers to enhance communication.
Example use case: Automatically send a custom sticker as a reaction to a user’s message in a chatbot flow to add personality and emotion.
Properties
| Name | Meaning |
|---|---|
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to which the sticker will be sent. |
| Sticker Source | Method to provide the sticker file: • Binary Data (from previous node) • Base64 encoded string • URL to the sticker file |
| Binary Property | Name of the binary property containing the sticker data when using Binary Data source. Default is "data". |
| Base64 Sticker | Base64 encoded sticker in WebP format (required if Sticker Source is Base64). |
| Sticker URL | URL to the sticker file (required if Sticker Source is URL). |
| Additional Options | Collection of optional settings: • Message ID: Custom message identifier (auto-generated if omitted) • Presence Simulation: Simulate typing/recording indicator duration in milliseconds (0-30000) • Message Duration: Disappearing message duration (No expiration, 24h, 7d, 90d) • Context Information: For replies, forwards, mentions (includes forward flag, mention all, mentioned users list, participant JID, reply message ID) |
Output
The node outputs JSON data representing the response from the ZuckZapGo API after attempting to send the sticker message. This includes status information about the message delivery.
If the "optimizeResponse" option is enabled, the output may be truncated or structured to reduce noise and improve AI processing efficiency.
No binary output is produced by this operation.
Dependencies
- Requires an active connection to the ZuckZapGo API via an API key credential configured in n8n.
- The node uses HTTP requests to communicate with the ZuckZapGo service endpoints.
- For binary sticker sources, the input data must contain valid binary data under the specified property.
Troubleshooting
- Binary Property Not Found: If using binary data as sticker source, ensure the specified binary property exists in the input item; otherwise, an error like
Binary property "X" not foundwill occur. - Invalid Sticker Format: Stickers must be in WebP format. Providing unsupported formats may cause failures.
- Missing Required Fields: When using Base64 or URL sources, the corresponding fields must be provided and non-empty.
- API Errors: Network issues or invalid credentials can cause request failures. Verify API key validity and network connectivity.
- Context Info Misconfiguration: Incorrectly formatted context info (e.g., malformed mention lists) may lead to unexpected behavior or errors.
Links and References
- ZuckZapGo GitHub Repository - Official documentation and source code for the ZuckZapGo API integration.