Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node allows sending interactive button messages through the Evolution API messaging service. It is designed to send a message containing up to three buttons, each of which can be configured to perform different actions such as replying with a preset text, copying a code, opening a URL, or initiating a phone call.
Common scenarios for this node include:
- Customer support bots that provide quick reply options.
- Marketing campaigns where users can click buttons to visit URLs or copy promotional codes.
- Automated systems that allow users to initiate calls or respond quickly via predefined replies.
For example, a business could send a message titled "Choose an option" with buttons like "Contact Support" (call), "Visit Website" (URL), and "Copy Discount Code" (copy).
Properties
Name | Meaning |
---|---|
Name Da Instância | The name of the instance that will send the buttons. |
Número Do Destinatário | The recipient's phone number or identifier to whom the message will be sent. |
Título | The title of the button message. |
Descrição | The description text of the button message. |
Rodapé | Footer text displayed at the bottom of the message (optional). |
Botões | Up to 3 buttons to include in the message. Each button has: |
- Tipo (Type): one of Reply, Copy, URL, or Call. | |
- Texto Do Botão (Button Text): the label shown on the button. | |
- ID: required if type is Reply; identifies the reply action. | |
- Código Para Copiar (Copy Code): required if type is Copy; the text/code to copy to clipboard. | |
- URL: required if type is URL; the link to open when clicked. | |
- Número De Telefone (Phone Number): required if type is Call; the phone number to call. |
Output
The node outputs a JSON array containing the response from the Evolution API after sending the button message. This typically includes confirmation details about the sent message, such as status or message IDs.
If the API supports binary data (e.g., media attachments), it would be included accordingly, but based on the provided information, the output focuses on JSON responses related to message sending.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-reference
for API requests. - Proper configuration of the API credential within n8n is necessary for successful operation.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you use the correct resource ("messages-api") and operation ("send-buttons").
- Missing Required Fields: The node requires certain fields like instance name, recipient number, title, description, and button details. Omitting these will cause errors.
- Button Configuration Errors: Each button type requires specific properties (e.g., "id" for reply buttons, "url" for URL buttons). Make sure all required fields per button type are filled.
- API Authentication Issues: Invalid or missing API credentials will prevent the node from sending messages. Verify your API key setup.
- Message Sending Failures: Network issues or incorrect recipient numbers may cause failures. Check logs and ensure the recipient identifier is valid.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes (for general guidance on node development)