Actions21
Overview
The "Send Buttons" operation of the ZuckZapGo AI node enables sending interactive WhatsApp messages containing clickable buttons. This feature is useful for creating engaging conversations where recipients can quickly respond or select options without typing. Typical use cases include customer support menus, quick polls, call-to-action prompts, and guided workflows in chatbots.
For example, a business could send a message with buttons like "Order Status," "New Product Info," and "Contact Support," allowing users to tap their choice and receive immediate relevant responses.
Properties
| Name | Meaning |
|---|---|
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to which the message is sent. |
| Message | The main text content of the button message. |
| Additional Options | Collection of optional settings: |
| - Message ID | Custom identifier for the message; auto-generated if omitted. |
| - Presence Simulation | Simulates typing or recording indicator for a specified duration (0-30000 ms). |
| - Message Duration | Sets WhatsApp disappearing message duration (No Expiration, 24 Hours, 7 Days, 90 Days). |
| - Context Information | Context for replies, forwards, mentions including forwarded flag, mention all, specific user mentions, reply message ID, and participant JID. |
Output
The node outputs a JSON object representing the API response from the ZuckZapGo service after sending the button message. This typically includes status information about the sent message, such as message ID, timestamps, and any errors if occurred.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ZuckZapGo API service.
- Needs an API key credential configured in n8n for authentication.
- The node uses internal helper functions to prepare media data and make HTTP requests to the ZuckZapGo endpoints.
Troubleshooting
- Missing Binary Property Error: If the node expects binary data (not applicable for Send Buttons but common in other operations), it throws an error if the specified binary property is not found.
- Invalid Recipient Format: Ensure the recipient phone number or group/newsletter/LID ID is correctly formatted, including the required suffixes like
@g.usfor groups. - API Request Failures: Network issues or invalid credentials will cause request failures. Verify API key validity and network connectivity.
- Context Information Misconfiguration: When using context info for replies or mentions, ensure all required fields like participant JID and stanza ID are correctly set to avoid message delivery issues.
Links and References
- ZuckZapGo GitHub Repository – Official documentation and source code for the ZuckZapGo API.
- WhatsApp Interactive Messages Documentation (general reference): https://developers.facebook.com/docs/whatsapp/api/messages/interactive
This summary focuses on the "Send Buttons" operation within the ZuckZapGo AI node, describing its purpose, inputs, outputs, dependencies, and common troubleshooting tips based on static analysis of the provided source code and property definitions.