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
- Webhooks Actions
- Teams Actions
- Custom Filters 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 interactions 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 state of the conversation after the priority change. This typically includes confirmation that the priority was successfully updated and may contain details about the conversation such as its ID and new priority status.
If the node supports binary data output (not indicated here), it would generally relate to attachments or media associated with the conversation, but this operation focuses solely on updating metadata (priority).
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 conversation priority updates.
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: Providing a priority value outside the allowed options will result in a validation error. Use one of the specified priority levels: Urgent, High, Medium, Low, or None.
- API Rate Limits: Frequent updates might hit rate limits imposed by the ChatWoot API. Implement retry logic or reduce request frequency if errors occur.
Links and References
- ChatWoot API Documentation – Official API docs for reference on conversation management.
- ChatWoot GitHub Repository – Source code and community support.