Actions100
- 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
Overview
This node allows you to toggle (change) the status of a conversation in ChatWoot, a customer support platform. It is useful for automating workflows where you need to programmatically update the state of conversations—such as marking them as open, resolved, or pending—based on certain triggers or business logic.
Practical examples:
- Automatically mark a conversation as "resolved" after sending a closing message.
- Set a conversation to "pending" if awaiting further information from a customer.
- Reopen a conversation when a new message is received.
Properties
| Display Name | Type | Description |
|---|---|---|
| Account Id | Number | The numeric ID of the account. |
| Conversation Id | Number | The numeric ID of the conversation. |
| Status | Options | The status to set for the conversation. Possible values: Open, Resolved, Pending. |
Output
The output will be a JSON object representing the updated conversation. The structure typically includes fields such as the conversation's ID, current status, and other metadata returned by the ChatWoot API after the status change.
{
"id": 12345,
"status": "resolved",
// ...other conversation fields
}
Note: The exact fields depend on the ChatWoot API response.
Dependencies
- External Service: Requires access to a ChatWoot instance.
- API Key: You must provide valid ChatWoot API credentials (
chatwootApi). - n8n Configuration: The base URL for your ChatWoot instance should be set in the credentials.
Troubleshooting
- Invalid Account or Conversation ID: If you provide an incorrect Account Id or Conversation Id, the node may return a "Not Found" or similar error from the ChatWoot API. Double-check these IDs.
- Authentication Errors: If your API key or credentials are missing or invalid, you'll receive authentication errors. Ensure your
chatwootApicredentials are correctly configured in n8n. - Status Value Issues: Only the allowed status values ("open", "resolved", "pending") are accepted. Using any other value will result in an error.