Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Mark as Unread," it allows users to mark a particular chat message as unread. This can be useful in scenarios where you want to programmatically flag messages that require attention or follow-up, such as customer support chats or personal reminders.
For example, after processing incoming messages, you might want to mark certain messages as unread to ensure they are reviewed later.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance (likely the chat client or account) to use for the operation. |
| Contato | The contact number associated with the chat message to mark as unread. |
| Message ID | 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/false). |
Output
The node outputs a JSON array containing the result of the "mark as unread" operation. The exact structure depends on the Evolution API response but typically 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 base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential within n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "chat" and "mark-unread" respectively.
- Missing Required Parameters: Ensure all required properties (
instanceName,chat,messageId,fromMe) are provided; missing any will likely cause errors. - Authentication Issues: Confirm that the API key credential is valid and has the necessary permissions.
- API Endpoint Errors: Network issues or incorrect base URL configurations may cause request failures.
Links and References
- Evolution API Documentation (official API reference)