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 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 more effectively. For example, a support agent might mark a conversation as "Urgent" to prioritize it for immediate attention or set it to "Low" if it requires less urgent follow-up.
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 being toggled. |
| Priority | The new priority level to assign to 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's state. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The node depends on the ChatWoot REST API endpoint that manages conversation priorities.
- Proper configuration of the base URL for the ChatWoot instance is necessary in the node credentials.
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 is correctly configured and has sufficient permissions.
- Invalid Priority Value: Providing a priority value outside the allowed options (urgent, high, medium, low, none) may result in validation errors. Use only the specified options.
- Network Issues: Connectivity problems with the ChatWoot server can cause timeouts or failed requests. Check network access and server availability.