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 priority level of a specific conversation within an account on the ChatWoot platform. It allows users to update the urgency or importance of conversations, which can help in managing customer support tickets or chat threads by categorizing them according to their priority.
Common scenarios include:
- Automatically escalating conversations marked as urgent for faster response.
- Downgrading conversations that no longer require immediate attention.
- Organizing conversations by priority to streamline workflow and resource allocation.
For example, a support team might use this node to mark a conversation as "Urgent" when a VIP customer reports a critical issue, ensuring it gets immediate attention.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the conversation exists. |
| Conversation Id | The numeric ID of the conversation whose priority is to be toggled. |
| Priority | The new priority level to set for the conversation. Options: Urgent, High, Medium, Low, None |
Output
The node outputs JSON data representing the updated conversation object after the priority change. This typically includes details such as the conversation ID, updated priority status, timestamps, and possibly other metadata related to the conversation.
If binary data is returned (not indicated here), it would generally represent attachments or media associated with the conversation, but this operation focuses on updating priority and thus primarily returns JSON.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- Needs the base URL of the ChatWoot instance configured in the credentials.
- Depends on the ChatWoot REST API endpoint for updating conversation priority.
Troubleshooting
- Invalid Account or Conversation ID: Ensure that the provided numeric IDs correspond to existing entities in ChatWoot. Errors may occur if these IDs are incorrect or do not exist.
- Authentication Errors: Verify that the API key credential is valid and has sufficient permissions to modify conversations.
- Priority Value Issues: Only the specified priority options ("urgent", "high", "medium", "low", "none") are accepted. Using unsupported values will cause errors.
- Network or API Endpoint Issues: Confirm that the ChatWoot instance URL is reachable and the API endpoint is available.
Links and References
- ChatWoot API Documentation - Official API docs for reference on conversation management.
- n8n Documentation - For general guidance on using n8n nodes and credentials.