Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node integrates with the Evolution API to send interactive poll messages via a messaging platform. Specifically, the "Enviar Enquete" operation under the "Mensaje" resource allows users to create and send a poll with multiple unique options to a specified recipient number from a given instance.
Common scenarios include:
- Collecting feedback or opinions from users in chat groups or direct messages.
- Running quick surveys or votes within messaging apps.
- Engaging audiences interactively by sending polls directly through automated workflows.
For example, a marketing team could use this node to send a poll asking customers which product feature they prefer, collecting responses directly in their messaging app.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance that will send the poll message. |
| Número Del Destinatario | The recipient's phone number or identifier where the poll will be sent. |
| Título De La Encuesta | The title or caption of the poll message. |
| Opciones De La Encuesta | The poll options; must be between 2 and 12 unique choices. |
| Retraso | Delay in milliseconds before the message is sent (default 1200 ms). |
| Responder Mensaje | Optionally reply to a specific message by providing its ID. |
| Menciones | Settings for mentions: either mention all group participants or specify a comma-separated list of numbers. |
Output
The node outputs a JSON array containing the response from the Evolution API after sending the poll. This typically includes metadata about the sent message such as message IDs, status, timestamps, or any error information returned by the API.
If the API supports binary data (e.g., media attachments), it would be included accordingly, but based on the provided properties and code, the output focuses on JSON metadata related to the poll message.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the instance name and recipient number is necessary for successful message delivery.
Troubleshooting
Common Issues:
- Invalid or missing instance name or recipient number can cause message sending failures.
- Providing fewer than 2 or more than 12 poll options, or duplicate options, may result in errors.
- Incorrect message ID when replying to a message can cause the reply to fail.
- Network or authentication issues with the Evolution API will prevent message delivery.
Error Messages:
"Operação não suportada."indicates the selected operation-resource combination is not implemented.- API errors returned from Evolution API will be passed through; check the error details for invalid parameters or authorization failures.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure poll options meet uniqueness and count requirements.
- Confirm API credentials are valid and have necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes for further customization guidance