Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The "Mark as Unread" operation in the Chat resource of this node allows users to mark a specific message in a chat conversation 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. For example, if an automated workflow processes incoming messages but wants to remind the user to review certain messages manually, marking them as unread helps maintain visibility.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance (account or environment) from which the chat message originates. |
| Contact | The contact number associated with the chat conversation where the message exists. |
| Message ID | The unique identifier of the last message to be marked as unread. |
| Is My Message | Boolean indicating whether 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 API response but typically includes confirmation of the action or updated message status. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential to authenticate requests to the Evolution API.
- The base URL for API requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the Resource is set to "Chat" and Operation to "Mark as Unread".
- Missing required parameters: Ensure all required properties (Instance Name, Contact, Message ID, Is My Message) are provided; missing any will cause errors.
- Authentication failures: Confirm that the API key credential is correctly configured and has sufficient permissions.
- Invalid Message ID or Contact: Errors may occur if the message ID or contact number does not exist or is incorrect; double-check these values.
Links and References
- Evolution API Documentation (official API reference for further details on endpoints and parameters)