Actions48
- Account Actions
- Blacklist Actions
- Campaign Actions
- Conversation Actions
- Custom Variable Actions
- Label Actions
- Lead Actions
- Template Actions
- Webhook Actions
Conversation → Mark Conversation As Read
AI-generatedOverview
This node operation marks a specified conversation as read in the Aimfox application. It is useful for managing conversation states, ensuring that conversations are updated to reflect that they have been viewed or processed. For example, it can be used in workflows that automate message handling or customer support ticket updates.
Use Case Examples
- Mark a LinkedIn conversation as read after processing messages.
- Automatically update conversation status in Aimfox to read after a user interaction.
Properties
| Name | Meaning |
|---|---|
| Conversation URN | The URN of the conversation to mark as read, uniquely identifying the conversation. |
| Account ID | The LinkedIn ID of the account associated with the conversation to be marked as read. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to customize the API request behavior. |
Output
JSON
status- The status of the mark as read operation, indicating success or failure.conversationUrn- The URN of the conversation that was marked as read.accountId- The LinkedIn account ID associated with the conversation.
Dependencies
- An API key credential for Aimfox API authentication
Troubleshooting
- Ensure the Conversation URN and Account ID are correctly provided and valid; otherwise, the API call may fail.
- Check network connectivity and proxy settings if requests time out or fail to connect.
- If SSL issues occur, consider enabling the option to ignore SSL certificate validation, but be aware of security risks.
- Verify that the API key credential is correctly configured and has the necessary permissions to mark conversations as read.