Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource "Mensagem" and operation "Enviar Texto," it sends a text message to a specified recipient via the Evolution API. This is useful in scenarios where automated or programmatic sending of text messages is required, such as customer notifications, alerts, or chatbots.
For example, you can use this node to send a welcome message to new users, notify customers about order status updates, or reply automatically to incoming messages.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance that will send the message. |
| Numero Do Destinatario | The recipient's remote JID (unique identifier for the destination). Required. |
| Mensagem | The text message content to be sent. Required. |
| Opções | Additional options for sending the message: |
| - Delay | Number of milliseconds to wait before sending the message (default 1200 ms). |
| - Responder Mensagem | Option to reply to a specific message by providing its ID. |
| - Menções | Settings for mentions within the message: |
| - Mencionar Todos | Boolean to mention all participants in a group. |
| - Números Para Mencionar | Comma-separated list of numbers to mention individually (only if not mentioning all). |
| - Preview De Link | 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 API supports binary data (e.g., media attachments), this node does not handle them in this operation; it focuses solely on sending text messages.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - No additional external dependencies are indicated.
Troubleshooting
Common Issues:
- Missing or incorrect recipient identifier (
remoteJid) will cause the message to fail. - Invalid or expired API credentials will result in authentication errors.
- Network connectivity issues may prevent the node from reaching the Evolution API.
- Providing invalid message IDs when replying to messages can cause errors.
- Missing or incorrect recipient identifier (
Error Messages:
"Operação não suportada."indicates the requested operation is not supported by the node.- API errors returned from the Evolution API will be passed through; check the error message for details.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure API credentials are valid and have necessary permissions.
- Confirm network access to the Evolution API endpoint.
- Double-check message IDs used for replies.
Links and References
- Evolution API Documentation (official API reference)