Actions115
- Teams Actions
- Account Users Actions
- Custom Attributes Actions
- Contacts Actions
- Conversation Labels Actions
- Reports Actions
- Accounts Actions
- Contact Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Messages Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Inboxes Actions
- Integrations Actions
- Profile Actions
- Custom Filters Actions
- Webhooks Actions
Overview
This node operation toggles the status of a conversation within an account on the Konverte Digital platform. It is useful for managing conversation workflows by updating the conversation's status to open, resolved, or pending. For example, customer support teams can use this node to mark conversations as resolved after addressing customer issues or set them to pending if awaiting further information.
Use Case Examples
- Updating a conversation status to 'resolved' after issue resolution.
- Setting a conversation status to 'pending' when waiting for customer response.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the conversation belongs. |
| Conversation Id | The numeric ID of the conversation whose status is to be toggled. |
| Status | The new status to set for the conversation. Options include 'open', 'resolved', and 'pending'. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and request timeout. |
Output
JSON
status- The updated status of the conversation after the toggle operation.conversation_id- The ID of the conversation whose status was toggled.account_id- The ID of the account associated with the conversation.
Dependencies
- Requires an API key credential for authentication with the Konverte Digital API.
Troubleshooting
- Ensure the account_id and conversation_id are valid numeric IDs; invalid IDs will cause the request to fail.
- Verify that the API key credential is correctly configured and has the necessary permissions to update conversation statuses.
- If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option, but be aware of the security implications.
- Check proxy settings if requests are failing due to network restrictions or firewall rules.
- Timeout errors may occur if the server is slow to respond; increase the timeout setting if necessary.