Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API to perform various operations on different resources. Specifically, for the Chat resource and the Mark as Unread operation, it allows users to mark a particular chat message as unread. This can be useful in scenarios where you want to flag messages for follow-up or indicate that a message requires attention later.
Practical examples include:
- Automatically marking incoming messages as unread if they meet certain criteria.
- Managing message states programmatically in customer support workflows.
- Integrating with other systems to synchronize message read/unread status.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API instance. |
| Contato | The contact number associated with the chat where the message is located. |
| ID Da Mensagem | The unique identifier of the last message to be marked as unread. |
| Mensagem É Minha | Boolean indicating whether the message was sent by the instance (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 details about the updated message state.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL and headers to be configured internally.
- Proper configuration of the instance name and valid contact/message IDs are necessary for successful execution.
Troubleshooting
- Operation not supported error: If the operation or resource is not recognized, ensure that the correct resource ("chat") and operation ("mark-unread") are selected.
- Invalid or missing parameters: Make sure all required properties (instance name, contact number, message ID, and fromMe flag) are provided and correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Message not found: If the message ID does not exist or is incorrect, the API may return an error; double-check the message ID.
- Network issues: Ensure the node can reach the Evolution API endpoint without firewall or connectivity problems.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes