Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" is designed to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Search Status" (referred to as "find-status-messages" in the properties), it allows users to search for status messages related to a chat contact within an instance of the Evolution API environment.
This node is beneficial when you need to programmatically retrieve message status information such as read receipts or delivery confirmations for specific messages in a chat system. For example, a user might want to check if a particular message sent to a contact has been read or delivered, paginate through status messages, or audit message statuses for compliance or analytics.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance where the chat data resides; identifies the Evolution API instance to query. |
| Contato | The contact's number (remoteJid) whose message status is being searched. |
| Message ID | The unique identifier of the message for which status messages are requested. |
| Página | The page number for paginated results, allowing navigation through multiple pages of status messages. |
| Quantidade Por Página | The number of status messages to return per page, controlling the size of each result set. |
Output
The node outputs a JSON array containing the results of the status message search. Each item in the array represents a status message related to the specified message ID and contact within the given instance. The exact structure of each status message object depends on the Evolution API response but typically includes details like status type, timestamps, and possibly metadata about the message state.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - The node expects the Evolution API to be accessible and properly configured with valid credentials in n8n.
- No other external dependencies or environment variables are explicitly required based on the static analysis.
Troubleshooting
- Unsupported Operation Error: If the operation specified is not supported, the node throws an error stating that the function for the resource-operation combination is not supported. Ensure that the operation name matches exactly one of the implemented functions.
- Missing Required Parameters: Since properties like instance name, contact number, and message ID are required, missing any of these will likely cause errors or empty responses. Verify all required inputs are provided.
- API Connectivity Issues: Network problems or invalid API credentials can cause request failures. Check API key validity and network access to the Evolution API endpoint.
- Pagination Misconfiguration: Providing invalid page numbers or offsets may result in unexpected results or empty arrays. Use sensible pagination values.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n Documentation on Creating Custom Nodes (for general understanding of node development)
Note: The actual implementation of the search status operation logic is abstracted in the bundled source under a.resourceOperationsFunctions[o][t] and is not fully visible here. The summary is based on the provided properties and node structure.