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
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Conversations → Toggle Status Of A Conversation
AI-generatedOverview
This node operation allows users to toggle the status of a conversation within an account on the ChatWoot platform. It is useful for managing customer support conversations by updating their state, such as marking them as open, resolved, or pending. Practical scenarios include automating workflow steps where conversations need to be programmatically closed after resolution or reopened if further action is required.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the conversation belongs. |
| Conversation Id | The numeric ID of the specific conversation whose status you want to change. |
| Status | The new status to set for the conversation. Options: Open, Resolved, Pending. |
Output
The node outputs JSON data representing the updated conversation object after the status change. This typically includes details such as the conversation ID, updated status, timestamps, and possibly other metadata related to the conversation's current state. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- Needs the base URL of the ChatWoot instance configured in the node credentials.
- Relies on the ChatWoot REST API endpoint that handles conversation status updates.
Troubleshooting
- Invalid Account or Conversation ID: If the provided IDs do not exist or are incorrect, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly configured.
- Status Value Errors: Providing a status value outside the allowed options (open, resolved, pending) may result in validation errors. Use only the supported status values.
- Network Issues: Connectivity problems with the ChatWoot server can cause timeouts or request failures. Check network access and server availability.
Links and References
- ChatWoot API Documentation - Official API docs for reference on conversation management endpoints.