Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node allows you to send interactive WhatsApp messages with up to three custom buttons using the Evolution API. It is designed for scenarios where you want to engage users with quick reply options, links, phone calls, or copyable codes directly within a WhatsApp conversation. Typical use cases include customer support bots, marketing campaigns, appointment scheduling, and any workflow requiring user interaction via WhatsApp.
Practical Example:
A business can use this node to send a message like "How can we help you today?" with buttons such as "Talk to Support", "Visit Website", or "Call Us".
Properties
Below are the input properties supported by this operation:
| Display Name | Type | Description |
|---|---|---|
| Nome Da Instância | String | Digite o nome da instância que vai enviar os botões (Name of the instance sending the buttons). Required |
| Número Do Destinatário | String | WhatsApp number of the recipient. Required |
| Título | String | Title of the message containing the buttons. Required |
| Descrição | String | Description text shown in the message. Required |
| Rodapé | String | Footer text displayed at the bottom of the message. |
| Botões | Fixed Collection (up to 3) | The buttons to display in the message. Each button supports: - Tipo (Type): Options are Resposta (Reply), Copiar (Copy), URL, Ligar (Call). - Texto Do Botão: Button label. Required - ID: Required if type is Reply. - Código Para Copiar: Required if type is Copy. - URL: Required if type is URL. - Número De Telefone: Required if type is Call. |
Output
The output will be a JSON object (or array of objects) representing the result of the API call to Evolution API. The structure typically includes:
- status: Indicates success or failure.
- messageId: Unique identifier for the sent message.
- details: Additional information about the sent message or error details.
Note: The exact fields may vary depending on the API response from Evolution API.
Dependencies
- External Service: Requires access to the Evolution API.
- API Key/Credentials: You must configure valid Evolution API credentials in n8n under the name
evolutionApi. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common Issues:
Missing Required Fields: If any required property (such as Nome Da Instância, Número Do Destinatário, Título, Descrição, or required button fields) is missing, the node will throw an error indicating which field is missing.
Unsupported Operation: If you select an unsupported resource or operation, you may see an error like:
Operação não suportada. A função "send-buttons" para o recurso "messages-api" não é suportada!Resolution: Double-check that you have selected the correct resource and operation.
Invalid Credentials: If your Evolution API credentials are incorrect or missing, authentication errors will occur.
Resolution: Ensure your credentials are correctly configured in n8n.Button Limit Exceeded: Only up to 3 buttons are allowed per message.
Resolution: Reduce the number of buttons to 3 or fewer.