Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The "Mark as Unread" operation in the Chat resource of this node allows users to mark a specific chat message as unread within an Evolution API-powered chat instance. This is useful for scenarios where you want to flag messages for follow-up or remind yourself or others that a particular message requires attention later.
Practical examples include:
- Marking important customer support messages as unread to ensure they are revisited.
- Flagging team chat messages that need further discussion.
- Managing personal chat workflows by marking messages as unread after reading them accidentally.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the chat instance where the message exists. |
| Contact | The contact number associated with the chat conversation. |
| Message ID | The unique identifier of the message to be marked as unread. |
| Message Is Mine | 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 as unread" operation. Typically, this will include confirmation details such as success status or updated message metadata. The exact structure depends on the Evolution API response but generally confirms that the message's unread status has been updated.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Evolution API service.
- An API authentication token or key credential must be configured in n8n to authorize requests.
- Network access to
https://doc.evolution-api.com/api-referenceor the actual Evolution API endpoint.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the Resource is set to "Chat" and Operation to "Mark as Unread".
- Authentication errors: Ensure the API credentials are correctly configured and have sufficient permissions.
- Invalid message ID or contact: Double-check that the provided message ID and contact number exist and are correct; otherwise, the API may reject the request.
- Network issues: Confirm network connectivity to the Evolution API endpoint.
Links and References
- Evolution API Documentation (for detailed API usage and parameters)