Actions113
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response 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 resolved but requires additional follow-up.
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.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token configured in the node credentials.
- 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: Ensure the API key/token is valid and has sufficient permissions to modify conversations.
- Status Value Errors: Only the specified statuses ("open", "resolved", "pending") are accepted. Using any other value will cause the request to fail.
- Network Issues: Connectivity problems with the ChatWoot server can cause timeouts or failures. Check network access and endpoint availability.
Links and References
- ChatWoot API Documentation - For detailed API endpoints and payload structures.
- ChatWoot Official Website - To learn more about the platform features.