Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node allows sending a structured interactive list message via the Evolution API messaging service. It is designed to send a list with multiple sections and rows, where each row represents an option that the recipient can select. This type of message is useful for presenting users with a menu or choices in a conversational interface, such as customer support bots, surveys, or interactive notifications.

Practical examples:

  • Sending a product catalog with categories (sections) and items (rows) for customers to choose from.
  • Presenting a menu of services or options in a chatbot conversation.
  • Collecting user preferences by letting them pick from predefined options.

Properties

Name Meaning
Nombre De La Instancia The name of the instance that will send the list message.
Número Del Destinatario The recipient's phone number or identifier to whom the list will be sent.
Título De La Lista The main title of the list message.
Descripción Description text providing additional context about the list.
Texto Del Botón Text displayed on the button that opens the list options (default: "Ver Opciones").
Texto Del Pie De Página Footer text shown at the bottom of the list message.
Secciones One or more sections containing rows (options). Each section has:
- Título De La Sección: Title of the section.
- Filas: Multiple rows within the section, each with:
- Título: Title of the row (required).
- Descripción: Optional description of the row.
- ID De La Fila: Unique identifier for the row option.
Opciones Additional message options including:
- Retraso Delay in milliseconds before sending the message (default 1200 ms).
- Responder Mensaje Optionally reply to a specific message by providing its ID.
- Menciones Mention settings:
- Mencionar a Todos: Boolean to mention all group participants.
- Números Para Mencionar: Comma-separated list of numbers to mention individually (if not all).

Output

The node outputs a JSON array where each item corresponds to the result of sending the list message. The exact structure depends on the Evolution API response but generally includes confirmation details such as message IDs, status, or error information.

If the node supports binary data output, it would typically represent media attachments or files related to the message, but this operation focuses on sending text-based interactive lists, so no binary output is expected.

Dependencies

  • Requires an active Evolution API credential configured in n8n for authentication.
  • Depends on the Evolution API endpoint to send messages.
  • Network connectivity to the Evolution API service.

Troubleshooting

  • Common issues:

    • Missing or invalid instance name or recipient number will cause the message to fail.
    • Incorrectly formatted sections or rows (e.g., missing required titles or IDs) may lead to errors.
    • API authentication failures if credentials are not set up properly.
    • Network timeouts or delays if the API service is unreachable.

  • Error messages:

    • "Operação não suportada." indicates the selected operation is not supported by the node.
    • Validation errors related to missing required fields like recipient number or list title.
    • API errors returned from the Evolution API, which should be checked for detailed messages.

To resolve these, ensure all required properties are correctly filled, verify API credentials, and check network connectivity.

Links and References

Discussion