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
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Mensaje" and Operation "Enviar Texto", it allows sending text messages to a specified recipient remotely. This is useful in scenarios where automated or programmatic messaging is required, such as customer notifications, alerts, or chatbots.
For example, you can use this node to send a customized text message to a user’s phone number, optionally mentioning other users in a group chat, replying to a previous message, or controlling link previews in the message content.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance that will send the message. |
| Número Del Destinatario | The remoteJid (identifier) of the message recipient. |
| Mensaje | The text content of the message to be sent. |
| Opciones | Additional options for sending the message: |
| - Retraso | Delay in milliseconds before the message is sent (default 1200 ms). |
| - Responder Mensaje | ID of the message to which this message will reply. |
| - Menciones | Settings for mentions within the message: |
| -- Mencionar a Todos | Boolean to mention all participants in a group chat. |
| -- Números Para Mencionar | Comma-separated list of numbers to mention individually (used if not mentioning everyone). |
| - Vista Previa De Enlace | Boolean to enable or disable link preview in the message (default enabled). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the text message. The exact structure depends on the API response but typically includes confirmation details such as message ID, status, timestamps, or error information if the sending failed.
If the node supports binary data output (not indicated here), it would represent any media or attachments sent alongside the message, but for this operation, the focus is on text message sending.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- Network access to
https://doc.evolution-api.com/api-referenceor the actual Evolution API endpoint. - Proper configuration of the node properties to specify recipient and message details.
Troubleshooting
Common Issues:
- Missing or incorrect recipient identifier (
remoteJid) will cause message sending to fail. - Invalid or expired API credentials will result in authentication errors.
- Network connectivity issues may prevent reaching the Evolution API.
- Improperly formatted message text or unsupported characters might cause rejection by the API.
- Missing or incorrect recipient identifier (
Error Messages:
"Operação não suportada."indicates the selected operation is not supported for the chosen resource; verify correct resource-operation selection.- Authentication errors suggest checking API key validity and permissions.
- Timeout or network errors require verifying internet connection and API availability.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes for further customization guidance