Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração 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 chat message from a given contact on a specified instance. This is useful in scenarios where you want to programmatically access individual messages for processing, logging, or automation purposes.
Practical examples include:
- Fetching a particular message by its ID to analyze its content.
- Retrieving messages sent or received by the instance for audit or monitoring.
- Integrating chat message retrieval into workflows that trigger based on message content or metadata.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance from which to read the message. |
| Contato | The contact number (remote JID) associated with the chat message. |
| 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 (true) or received (false). |
Output
The node outputs a JSON array containing the data of the requested chat message. Each item in the output array corresponds to one message object with details as returned by the Evolution API. The exact structure depends on the API response but typically includes message content, sender information, timestamps, and message metadata.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API service to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Operation Not Supported Error: If the operation "Ler Mensagens" is not recognized, ensure that the resource and operation names are correctly set and supported by the node version.
- Missing Required Parameters: The properties "Nome Da Instância", "Contato", and "ID Da Mensagem" are mandatory. Omitting any will cause errors.
- Authentication Failures: Verify that the API key credential is valid and has sufficient permissions.
- Message Not Found: If the message ID does not exist or is incorrect, the API may return an error or empty result.
- Network Issues: Ensure the Evolution API endpoint is reachable from the n8n instance.
Links and References
- Evolution API official documentation (not provided in source; check vendor site)
- n8n documentation on creating custom nodes and using credentials
- General REST API usage guidelines