Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The "Enviar Lista" operation of the "Mensagem" resource in this node allows sending a structured list message through an Evolution API instance. This type of message is commonly used in chatbots or messaging automation to present users with a menu or multiple selectable options organized into sections. It is beneficial for scenarios such as customer support menus, product catalogs, or interactive surveys where users can pick from predefined choices.
For example, a business could send a list of service categories (each as a section) with individual services as rows, allowing customers to select what they want directly from the chat interface.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution API instance that will send the list message. |
| Número Do Destinatário | The recipient's phone number or identifier to whom the list message will be sent. |
| Título Da Lista | The main title of the list message, displayed prominently at the top. |
| Descrição | A description text providing additional context or information about the list. |
| Texto Do Botão | The label text shown on the button that opens the list options (e.g., "Ver Opções"). |
| Texto Do Rodapé | Footer text displayed at the bottom of the list message. |
| Seções | One or more sections within the list, each containing: - Título Da Seção: Title of the section. - Linhas: Multiple rows representing options, each with: - Título (required): Option title. - Descrição (optional): Description of the option. - ID Da Linha: Unique identifier for the option. |
| Opções (Options) | Additional message options including: - Delay: Milliseconds delay before sending the message. - Responder Mensagem: Optionally reply to a specific message by its ID. - Menções: Mention settings: - Mencionar Todos: Whether to mention all group participants. - Números Para Mencionar: Specific numbers to mention, comma-separated. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the list message. The exact structure depends on the API but typically includes confirmation details such as message IDs, status, or error information.
If binary data were involved (e.g., media files), it would be summarized here, but this operation focuses on sending structured text lists only.
Dependencies
- Requires an active Evolution API instance configured with appropriate credentials (an API key or token).
- The node expects the Evolution API base URL and authentication to be set up correctly in n8n credentials.
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Missing required fields such as instance name, recipient number, or list title will cause errors.
- Incorrect formatting of sections or rows (e.g., missing row titles or duplicate row IDs) may lead to API rejection.
- Invalid recipient identifiers or network issues can prevent message delivery.
Error Messages:
"Operação não suportada."indicates the selected operation is not implemented; ensure "Enviar Lista" is chosen under the correct resource.- API errors returned from Evolution API might include authentication failures or invalid payloads; verify credentials and property values.
Resolutions:
- Double-check all required properties are filled and formatted correctly.
- Confirm the Evolution API credentials are valid and have necessary permissions.
- Use the node's test button or logs to inspect request/response details for debugging.
Links and References
- Evolution API Documentation — Official API reference for message sending capabilities.
- n8n Documentation on Creating Custom Nodes — For understanding node development concepts.