Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node named "Evolution API" allows interaction with the Evolution API service. It supports multiple resources and operations, including a "Chat" resource with an operation to search for status messages ("Procurar Status"). This node is useful for retrieving message status information from a chat instance, such as checking delivery or read statuses of specific messages.
A practical example would be querying the status of a particular message sent to a contact within a specified chat instance, which can help in monitoring message delivery or troubleshooting communication issues.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the chat instance where the message resides. |
| Contato | The contact number (remote JID) associated with the message status to be searched. |
| ID Da Mensagem | The unique identifier of the message whose status is being queried. |
| Página | The page number for paginated results when retrieving status messages. |
| Quantidade Por Página | The number of status messages to retrieve per page (pagination size). |
Output
The node outputs a JSON array containing the results returned by the Evolution API for the requested operation. Each item in the array represents a status message or related data retrieved based on the input parameters.
If the node supports binary data output, it is not explicitly shown in the provided code snippet; thus, the output primarily consists of structured JSON data representing message statuses.
Dependencies
- Requires an API key credential for authenticating requests to the Evolution API.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - No additional external dependencies are indicated beyond the Evolution API service.
Troubleshooting
- Unsupported Operation Error: If the node throws an error stating that the operation is not supported, verify that the selected resource and operation names match those implemented in the node.
- Missing Required Parameters: Ensure all required properties such as instance name, contact number, and message ID are provided; missing these will likely cause request failures.
- API Authentication Issues: Confirm that the API key credential is correctly configured and valid to avoid authentication errors.
- Pagination Parameters: Incorrect page or offset values might result in empty or incomplete data sets; ensure these are set appropriately.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n Documentation on Creating Custom Nodes