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 Mark as Unread operation, this node marks a particular chat message as unread. This is useful in scenarios where you want to programmatically flag messages that require follow-up or attention, for example, in customer support workflows or automated messaging systems.
Practical examples include:
- Automatically marking incoming messages as unread if they meet certain criteria.
- Resetting the read status of messages after processing them in an external system.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API instance (e.g., https://api.exemplo.com). |
| API Key | The API key credential required to authenticate requests to the Evolution API. |
| Nome Da Instância | The name of the specific Evolution API instance you are targeting. |
| Contato | The contact number associated with the chat message to be marked as unread. |
| ID Da Mensagem | The unique identifier of the last message to mark as unread. |
| Mensagem É Minha | Boolean indicating whether the message was sent by the instance itself (true/false). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to mark the specified message as unread. The exact structure depends on the API's response but typically includes confirmation of the action or error details.
If the API supports binary data output, it is not indicated here; thus, the output is purely JSON-based.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Needs a valid API key credential for authentication.
- Proper configuration of the server URL and instance name is mandatory.
- No additional external libraries beyond those bundled with n8n are required.
Troubleshooting
Common Issues:
- Incorrect or missing API key will result in authentication errors.
- Invalid server URL or instance name may cause connection failures.
- Providing an incorrect message ID or contact number can lead to the operation failing silently or returning an error.
Error Messages:
"Operação não suportada."indicates that the selected operation is not implemented for the chosen resource.- Network or authentication errors will typically come from the underlying HTTP request and should be checked by verifying credentials and endpoint URLs.
Resolution Tips:
- Double-check all input parameters for correctness.
- Ensure the API key has sufficient permissions.
- Verify the Evolution API instance is reachable and operational.
Links and References
- Evolution API Documentation (as referenced in the code defaults)
- n8n Documentation on Creating Custom Nodes