Actions113
- Accounts Actions
- Account Users 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
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Webhooks Actions
- Teams Actions
- Custom Filters Actions
- Reports Actions
Overview
This node operation toggles the status of a conversation within an account on the ChatWoot platform. It allows users to update the state of a specific conversation by setting it to "open", "resolved", or "pending". This is useful in customer support workflows where conversations need to be tracked and managed according to their current handling status.
Practical examples include:
- Marking a conversation as resolved after the customer's issue has been addressed.
- Setting a conversation to pending if awaiting further information from the customer.
- Reopening a conversation that was previously closed to continue the discussion.
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: "Open", "Resolved", "Pending". |
Output
The node outputs JSON data representing the updated conversation object returned by the ChatWoot API after the status change. This typically includes details such as the conversation ID, updated status, timestamps, and other metadata related to the conversation.
If the node supports binary data output (not indicated here), it would generally represent attachments or media associated with the conversation, but this operation focuses on status toggling and thus primarily outputs JSON.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the ChatWoot instance must be provided in the credentials configuration.
Troubleshooting
- Invalid Account or Conversation ID: If the IDs provided do not exist or are incorrect, the API will return an error. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up.
- Status Value Errors: Providing a status value outside the allowed options ("open", "resolved", "pending") will result in a validation error. Use only the supported status values.
- Network Issues: Connectivity problems with the ChatWoot server can cause request failures. Check network access and endpoint availability.
Links and References
- ChatWoot API Documentation - Official API docs for reference on conversation management endpoints.
- ChatWoot Website - For general product information and support.