Actions64
- Instance Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
- Chat Actions
Overview
This node interacts with the Evolution API to perform various operations related to chat management. Specifically, the 'Mark As Unread' operation allows users to mark a particular message in a chat as unread. This can be useful in scenarios where a user wants to flag messages for follow-up or to ensure they revisit important communications later. For example, a customer support agent might mark a message as unread to remind themselves to respond later.
Use Case Examples
- Mark a message as unread in a chat to flag it for follow-up.
- Use the node to manage message read statuses programmatically within a chat application.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number associated with the chat where the message is located. |
| Message ID | The unique identifier of the message to be marked as unread. |
| Message Is From Me | A boolean indicating if the message was sent by the instance itself. |
Output
JSON
success- Indicates whether the message was successfully marked as unread.messageId- The ID of the message that was marked as unread.contact- The contact number associated with the chat where the message was marked unread.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
Troubleshooting
- Ensure the instance name is correctly specified and matches the configured Evolution API instance.
- Verify that the contact number and message ID are valid and exist in the chat system.
- Check that the API key credential has the necessary permissions to mark messages as unread.
- Common error: 'Unsupported operation' indicates the specified operation is not implemented or incorrectly named; verify the operation parameter.