Actions29
- Chat Actions
- Contact Actions
- Group Actions
- Message Actions
- Status Actions
Message → Send Interactive Buttons Reply (Beta)
AI-generatedOverview
This node operation sends a WhatsApp message with interactive reply buttons using the Green API. It allows users to specify a chat ID, optional message header and footer, the main message body, and up to three reply buttons. Each button has a unique identifier and display text. This operation is useful for creating interactive conversations where recipients can respond by clicking predefined buttons, enhancing user engagement and simplifying response collection.
Use Case Examples
- Sending a customer support message with quick reply buttons for common issues.
- Creating a poll or survey where users can select an option by clicking a button.
- Sending a notification with action buttons like 'Accept' or 'Decline'.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the chat to send the message to. For private chats, use phone@c.us; for group chats, use chatId@g.us. |
| Quoted Message ID | Optional ID of a message to quote in the reply. |
| Header | Optional message title displayed at the top of the message. |
| Body | The main text content of the message. Supports emoji symbols. |
| Footer | Optional message footer displayed at the bottom of the message. |
| Buttons | A collection of up to three reply buttons, each with a unique identifier and display text. |
Output
JSON
chatId- The chat ID to which the message was sent.body- The main text content of the sent message.buttons- Array of reply buttons included in the message, each with buttonId and buttonText.header- Optional header/title of the message.footer- Optional footer of the message.quotedMessageId- Optional ID of the quoted message if provided.messageId- The ID of the sent message returned by the API.
Dependencies
- Green API service with instance ID and API token credentials
Troubleshooting
- Ensure the chat ID is correctly formatted (phone@c.us for private chats, chatId@g.us for groups).
- Button IDs must be unique and button text must not exceed 25 characters.
- API credentials (instance ID and token) must be valid and not expired.
- Network issues or API endpoint errors can cause request failures; check error messages for details.
- If quoting a message, ensure the quotedMessageId is valid and exists in the chat.