Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource "Mensagem" and operation "Enviar Botões" (Send Buttons), it sends a message containing interactive buttons to a specified recipient via an instance of the Evolution API messaging system.
Common scenarios include:
- Sending interactive messages in customer support or marketing campaigns where recipients can respond by clicking buttons.
- Automating workflows that require user input through predefined button options.
- Enhancing chatbot interactions with quick reply buttons, URL links, copy-to-clipboard actions, or phone call triggers.
Practical example:
A business wants to send a promotional message with three buttons: one to reply with a preset answer, one to copy a discount code, and one to visit a URL. This node enables sending such a message programmatically.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance that will send the buttons message. |
| Número Do Destinatário | The recipient's phone number or identifier to whom the message with buttons will be sent. |
| Título | The title text of the message containing buttons. |
| Descrição | The description text of the message containing buttons. |
| Rodapé | Optional footer text displayed at the bottom of the message. |
| Botões | Up to 3 buttons included 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; unique identifier for the reply button | |
| - 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 dial |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the button message. The exact structure depends on the API response but typically includes status information about the message delivery.
If the API supports binary data (e.g., media attachments), this node does not explicitly handle binary output for this operation.
Dependencies
- Requires an active Evolution API instance configured in n8n with appropriate credentials (an API key or token).
- Network access to the Evolution API endpoint (
https://doc.evolution-api.com/api-reference). - Proper configuration of the node properties to match the target instance and recipient details.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "messages-api" and "send-buttons" respectively.
- Missing Required Fields: Ensure all required fields like instance name, recipient number, title, description, and button-specific fields are provided.
- API Authentication Errors: Check that the Evolution API credentials are valid and have necessary permissions.
- Button Limit Exceeded: The node limits buttons to a maximum of 3; exceeding this may cause errors.
- Invalid Button Type or Missing Button Data: Each button must have the correct fields filled based on its type; missing these will cause failures.
Links and References
- Evolution API Documentation (official API reference)
- n8n Documentation on Creating Custom Nodes