Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource Chat and Operation Ler Mensagens (Read Messages), it allows users to retrieve a specific message from a chat instance by specifying the instance name, contact number, and message ID. This is useful in scenarios where you want to programmatically fetch and process individual chat messages, for example, to archive conversations, analyze message content, or trigger workflows based on message data.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the chat instance from which to read the message. |
| Contato | The contact's phone number associated with the chat conversation. |
| ID Da Mensagem | The unique identifier of the message to be retrieved. |
| Mensagem É Minha | Boolean flag indicating if the message was sent by the instance itself (true/false). |
Output
The node outputs a JSON array containing the retrieved message data. Each item in the output corresponds to the message identified by the provided parameters. The structure of the JSON will include all relevant details of the message as returned by the Evolution API, such as message content, sender information, timestamps, and status.
If the node supports binary data (not explicitly shown in the code snippet), it would typically represent media attachments or files related to the message, but this is not indicated here.
Dependencies
- Requires an active connection to the Evolution API service.
- Requires an API authentication credential configured in n8n (an API key or token).
- The node depends on the Evolution API endpoint that supports reading messages by instance name, contact, and message ID.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error stating the operation is not supported. Ensure you use valid combinations of resource and operation.
- Missing Required Parameters: All properties marked as required must be provided; otherwise, the node will fail.
- API Authentication Issues: Make sure the API credentials are correctly set up and have sufficient permissions.
- Message Not Found: If the specified message ID does not exist for the given contact and instance, the API may return an error or empty result.
- Network or API Downtime: Connectivity issues with the Evolution API can cause failures; verify network access and API availability.
Links and References
- Evolution API official documentation (link not provided in source)
- n8n documentation on creating custom nodes and using API credentials: https://docs.n8n.io/
- General REST API best practices for error handling and authentication