Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Find Messages," it allows users to retrieve chat messages from a specified contact within an instance of the Evolution API environment. This operation supports pagination, enabling users to fetch messages page by page.
Common scenarios where this node is beneficial include:
- Retrieving historical chat messages for analysis or record-keeping.
- Integrating chat data into workflows for customer support or CRM systems.
- Automating message retrieval for monitoring or alerting purposes.
For example, a user can configure the node to fetch the first 10 messages from a particular contact's chat history in a given instance, then process or store these messages downstream in their workflow.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number (remote JID) whose messages are to be retrieved. |
| Page | The page number of the messages to retrieve (for pagination). Defaults to 1. |
| Quantity Per Page | The number of messages to retrieve per page. Defaults to 10. |
Output
The node outputs a JSON array containing the retrieved chat messages. Each element in the array represents a message object fetched from the Evolution API corresponding to the specified contact and page parameters.
If the Evolution API supports binary data in messages (e.g., media attachments), such data would typically be included in the output as binary fields, but this is not explicitly shown in the provided code snippet.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n (referred generically as an API key or token).
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - The node depends on internal helper functions mapped in
resourceOperationsFunctionsto execute specific resource-operation logic.
Troubleshooting
- Unsupported operation error: If the node throws an error stating that the function for the requested resource-operation is unsupported, verify that the resource and operation names are correctly specified and supported by the node.
- Authentication errors: Ensure that the required API credentials are properly configured and valid.
- Pagination issues: If no messages are returned, check if the page number and quantity per page parameters are within valid ranges and that the contact has messages.
- Network or API errors: Confirm network connectivity and that the Evolution API endpoint is reachable.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n documentation on Creating Custom Nodes