Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Chat → Mark As Unread
AI-generatedOverview
This node operation marks a specific chat message as unread in the Zapin EVO chat system. It is useful for scenarios where a user wants to flag a message to revisit later or indicate that the message has not been read yet. For example, it can be used in customer support workflows to ensure important messages are not overlooked.
Use Case Examples
- Mark a message as unread for a specific contact to remind the support agent to follow up later.
- Flag a message sent by the instance as unread to trigger a notification or further action.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Zapin EVO instance to interact with. |
| 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 | Boolean flag indicating if the message was sent by the instance itself. |
Output
JSON
success- Indicates if the message was successfully marked as unread.messageId- The ID of the message that was marked as unread.
Dependencies
- Requires an API key credential for authenticating with the Zapin EVO API.
Troubleshooting
- Ensure the instance name is correctly specified and matches the Zapin EVO instance.
- Verify the contact number and message ID are accurate and exist in the system.
- Check API credentials and permissions to confirm the node has access to modify message states.
- Common error: "Unsupported operation." indicates the operation or resource is not implemented or incorrectly specified.