Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a resource and operation, along with necessary parameters such as server URL and API key. Specifically, for the Chat resource and the Procurar Status (Find Status Messages) operation, it enables querying the status of chat messages by providing details like contact number, message ID, pagination, and instance name.
This node is beneficial in scenarios where you need to programmatically retrieve the status of specific chat messages from the Evolution API, for example:
- Tracking delivery or read status of messages sent to customers.
- Auditing communication logs for compliance or support purposes.
- Integrating chat status data into dashboards or CRM systems.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API endpoint (e.g., https://api.exemplo.com). |
| API Key | The API key credential for authenticating requests to the Evolution API instance. |
| Nome Da Instância | The name of the Evolution API instance you want to query. |
| Contato | The phone number of the contact whose message status you want to find. |
| ID Da Mensagem | The unique identifier of the message whose status is being queried. |
| Página | The page number for paginated results (default is 1). |
| Quantidade Por Página | The number of messages to return per page (pagination size, default is 10). |
Output
The node outputs a JSON array containing the results returned by the Evolution API for the requested chat message statuses. Each item in the array corresponds to a status message record matching the query parameters.
If the API supports binary data (not indicated here), the node would include that in the output accordingly, but based on the provided code and properties, the output is purely JSON structured data representing message status information.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires a valid API key credential for authentication.
- The node expects the user to provide the correct instance name and other parameters relevant to the Evolution API.
- No additional external dependencies are indicated beyond standard HTTP request capabilities.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you use valid combinations of resource and operation.
- Authentication errors: Invalid or missing API keys will cause authentication failures. Verify the API key is correct and has sufficient permissions.
- Invalid URL or network issues: Incorrect server URLs or network connectivity problems will prevent successful API calls. Confirm the URL and network access.
- Missing required parameters: All required fields such as contact number, message ID, and instance name must be provided; otherwise, the API call may fail or return incomplete data.
- Pagination parameters: Providing invalid page or offset values might result in empty or unexpected results. Use positive integers for these fields.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)
- For more detailed API usage, consult the official Evolution API docs or support channels.