Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Search Messages," it allows users to search and retrieve chat messages from a specified contact within an instance. This is useful in scenarios where you want to programmatically access message history, perform 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 for analysis or reporting.
- Automate responses or trigger actions based on message content.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance to connect to (required). |
| Contato | The contact number whose messages you want to find (required). |
| Página | The page number of the results to retrieve (default is 1). |
| Quantidade Por Página | Number of messages to return per page (default is 10). |
Output
The node outputs a JSON array containing the retrieved messages matching the search criteria. Each item in the array represents a message object with details as provided by the Evolution API. The exact structure depends on the API response but typically includes message content, sender, timestamp, and related metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
- The base URL for the API is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential in n8n is necessary for successful execution.
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 that the Resource is set to "chat-api" and Operation to "find-messages" for searching messages.
- Missing Required Parameters: The node requires the instance name and contact number. Omitting these will likely cause errors or empty results.
- API Authentication Issues: Invalid or missing API credentials will prevent the node from connecting to the Evolution API.
- Pagination Limits: Requesting pages beyond available data may return empty arrays; verify the total number of messages before paginating extensively.
Links and References
- Evolution API Documentation (official API reference)
- n8n Documentation on Creating Custom Nodes