Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node provides an interface to interact with the "Evolution API," specifically allowing users to find chat records based on given criteria. The "Find Chats" operation enables retrieving chat data filtered by contact and message identifiers, with support for pagination.
This node is useful in scenarios where you need to programmatically query chat histories or messages from a specific contact within an instance of the Evolution API service. For example, it can be used to fetch conversations related to a particular message ID or to paginate through chat records for analysis or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number (remote JID) whose chats are to be found. |
| Message ID | The specific message ID to filter chats. |
| Page | The page number of results to retrieve (for pagination). |
| Quantity Per Page | The number of chat records to return per page. |
Output
The node outputs a JSON array containing the chat records that match the specified filters. Each item in the output array represents a chat entry retrieved from the Evolution API based on the input parameters.
If the API supports binary data in chat records (e.g., attachments), this would typically be included in the JSON output or referenced accordingly, but no explicit binary output handling is indicated in the provided code.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n (referred to generically as an API key or token).
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the "Find Chats" operation is correctly selected and implemented in the node's resource-operation mapping.
- Missing required parameters: Ensure all required properties such as Instance Name, Contact, and Message ID are provided; missing these will likely cause API request failures.
- Pagination issues: If no results appear, check that the page number and quantity per page are set appropriately and that the requested page contains data.
- API connectivity errors: Confirm that the API credentials are valid and that the Evolution API endpoint is reachable from your environment.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on creating custom nodes for further customization guidance