Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node interacts with the Evolution API to perform various operations on different resources. Specifically, for the Chat resource and the Mark as Unread operation, it 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 later, such as automating customer support workflows or managing message states in bulk.
For example, after processing incoming messages, you might mark some as unread to remind agents to revisit them.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API. |
| Contato | The contact number associated with the chat where the message resides. |
| ID Da Mensagem | The unique identifier of the last message to be marked as unread. |
| Mensagem É Minha | Boolean indicating if the message was sent by the instance itself (true) or received (false). |
Output
The node outputs a JSON array containing the result of the "mark unread" operation. The exact structure depends on the Evolution API response but generally includes confirmation of the action or updated message status.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be reachable and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Operation Not Supported Error: If you see an error stating the operation is not supported, verify that the resource and operation names are correctly set to "chat" and "mark-unread" respectively.
- Authentication Failures: Ensure the API key credential is valid and has sufficient permissions.
- Invalid Message ID or Contact: Confirm that the message ID and contact number exist and are correctly formatted.
- Network Issues: Check connectivity to the Evolution API service.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using credentials