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 Procurar Mensagens (Find Messages), it allows users to search and retrieve chat messages from a specified contact within a given instance of the Evolution system. This is useful in scenarios where you want to programmatically access chat history, perform message audits, or integrate chat data into workflows.
For example, you might 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 analysis of chat conversations.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the Evolution instance to connect to. |
| 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 typically includes fields relevant to chat messages.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
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 in n8n.
- Invalid Contact or Instance Name: Providing incorrect contact numbers or instance names may result in empty results or errors. Double-check these inputs.
- Pagination Issues: Requesting pages beyond available data may return empty arrays. Adjust page and offset values accordingly.
Links and References
- Evolution API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes