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
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 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 is to be toggled. |
| Status | The new status to set for the conversation. Options: Open, Resolved, Pending. |
Output
The output JSON contains the response from the ChatWoot API after attempting to update the conversation status. This typically includes details about the updated conversation object reflecting the new status. The node does not output binary data.
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 are correct and correspond to existing resources.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update conversation statuses.
- Status Value Errors: Only the specified status options ("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 payloads)
- n8n Documentation (for general usage of custom nodes and credentials)