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 Priority Of A Conversation
AI-generatedOverview
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 low-priority conversations to focus on more critical issues.
- 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 state.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses solely on JSON data updates.
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 that handles updating conversation priorities.
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.
- Invalid Priority Value: Setting a priority outside the allowed options may result in validation errors. Use only the specified priority values: Urgent, High, Medium, Low, None.
- Network Issues: Connectivity problems with the ChatWoot server can cause timeouts or failed requests. Check network access and server availability.
Links and References
- ChatWoot API Documentation – Official API docs for reference on conversation management endpoints.
- n8n Documentation – For general guidance on using n8n nodes and credentials setup.