Actions113
- 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
- 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
Overview
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 examples include automatically resolving conversations after a support ticket is closed or reopening conversations when further follow-up is needed.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the conversation exists. |
| 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 returned from the ChatWoot API after toggling its status. This typically includes details such as the conversation's current status, timestamps, and other metadata reflecting the change. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node uses HTTP requests to interact with the ChatWoot REST API.
Troubleshooting
- Invalid Account or Conversation ID: If the provided IDs do not exist or are incorrect, the API will return an error. Verify that the IDs correspond to valid entities in your ChatWoot account.
- Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Status Value Errors: Only "open", "resolved", or "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 - Official API reference for managing conversations and statuses.
- n8n Documentation - General guidance on using n8n nodes and credentials.