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 "Procurar Mensagens" (Find Messages), it allows users to search and retrieve chat messages from a specified contact within a given instance. This is useful in scenarios where you want to programmatically access chat history, perform message audits, or integrate chat data into other workflows.
For example, you could use this node to:
- Retrieve recent messages exchanged with a particular contact.
- Paginate through chat history by specifying page number and messages per page.
- Automate monitoring or archiving of chat conversations.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance where the chat is hosted. |
| Contato | The contact's phone number or identifier whose messages you want to find. |
| Página | The page number of the results to retrieve (for pagination). |
| Quantidade Por Página | Number of messages to return per page (page size). |
Output
The node outputs a JSON array containing the retrieved chat messages matching the search criteria. Each item in the array represents a message object with details such as sender, timestamp, content, etc. The exact structure depends on the Evolution API response but generally includes message metadata and text.
There is no indication that the 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.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you use valid combinations of resource and operation.
- Authentication Failures: If the API key or credentials are invalid or missing, requests will fail. Verify that the API key credential is correctly set up.
- Empty Results: If no messages are found, check that the instance name and contact number are correct and that there are messages available for the specified page and offset.
- Pagination Issues: Providing invalid page numbers or offsets (e.g., negative values) may cause unexpected behavior or empty results.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using API credentials
- General REST API pagination concepts