Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração 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 (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 any relevant metadata about the message's delivery or read state.
If the API supports binary data (not indicated here), it would typically represent media or attachments related to the status messages, but this node appears focused on JSON data only.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API requests is
https://doc.evolution-api.com/api-reference. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource combination, the node throws an error indicating the function 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 input properties marked as required (instance name, contact, message ID). Omitting these will cause errors or empty responses.
- API Connectivity Issues: Network problems or invalid API credentials will result in request failures. Verify your API key and network access.
- Pagination Limits: Requesting pages beyond available data may return empty arrays; adjust the page and offset parameters accordingly.
Links and References
- Evolution API Documentation (official API reference)
- n8n Documentation on Creating Custom Nodes