Overview

This node operation marks a specific Unibox thread as read. It is useful in scenarios where users want to programmatically update the read status of email threads or conversations within the Unibox inbox, such as automating email management workflows or integrating with other systems to track message status.

Use Case Examples

1. Automatically mark a customer support email thread as read after processing it in a CRM system.
2. Mark marketing campaign response threads as read once they have been reviewed by the team.

Properties

Output

JSON

• id - The ID of the thread that was marked as read.
• status - The status result of the operation, indicating success or failure.

Dependencies

• Requires an API key credential for authenticating with the Instantly API to perform actions on Unibox threads.

Troubleshooting

• Common issues include providing an invalid or non-existent Thread ID, which will cause the operation to fail with an error indicating the thread could not be found.
• API authentication errors if the API key credential is missing or invalid, resulting in authorization failures.
• Network or connectivity issues when calling the Instantly API can cause timeouts or request failures.