Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Procurar Status" (translated as "Find Status Messages"), it allows users to query status messages related to a chat instance. This can be useful in scenarios where you want to retrieve message status information such as delivery or read receipts for a particular contact and message within a specified instance.
Practical examples include:
- Fetching the delivery status of a specific message sent to a contact.
- Paginating through status messages to analyze message engagement or troubleshoot message delivery issues.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the chat instance to query. |
| Contato | The contact number (remote JID) whose message status is being queried. |
| ID Da Mensagem | The unique identifier of the message for which status is requested. |
| Página | The page number for paginated results (default is 1). |
| Quantidade Por Página | Number of status messages to return per page (pagination size, default is 10). |
Output
The node outputs a JSON array containing the status messages retrieved from the Evolution API for the specified chat instance, contact, and message ID. Each item in the output array represents a status message record, likely including details such as status type, timestamp, and possibly other metadata related to the message's delivery or read state.
If the API supports binary data (e.g., media attachments), this node would handle it accordingly, but based on the provided code and properties, the primary output is structured JSON data representing message statuses.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- 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 operation is not supported. Ensure that the Resource is set to "chat-api" and Operation to "find-status-messages" for this functionality.
- Missing Required Parameters: The node requires all mandatory fields ("Nome Da Instância", "Contato", and "ID Da Mensagem") to be filled. Missing these will likely cause errors or empty responses.
- Pagination Issues: Incorrect values for "Página" or "Quantidade Por Página" might result in unexpected pagination behavior or no results. Use positive integers.
- API Connectivity: Network issues or invalid API credentials will prevent successful execution. Verify API keys and network access.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and handling API requests: https://docs.n8n.io/
- General REST API pagination concepts: https://restfulapi.net/pagination/