Actions113
- 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
- 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
Overview
This node integrates with the ChatWoot API to assign a conversation to either a specific user or a team within an account. It is useful in customer support workflows where conversations need to be routed to the appropriate agent or group for handling. For example, when a new customer message arrives, this node can automatically assign the conversation to a particular support agent or team based on workload or expertise.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account where the conversation exists. |
| Conversation Id | The numeric ID of the conversation to be assigned. |
| Assignee Id | The numeric ID of the user to whom the conversation will be assigned. If provided, this takes precedence over Team Id. |
| Team Id | The numeric ID of the team to which the conversation will be assigned. Ignored if Assignee Id is set. |
Output
The node outputs JSON data representing the result of the assignment operation as returned by the ChatWoot API. This typically includes details about the updated conversation, such as its new assignee or team. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL of the ChatWoot instance must be configured in the credentials.
- Uses the ChatWoot REST API endpoint for assigning conversations.
Troubleshooting
- Missing or invalid Account Id or Conversation Id: The API call will fail if these required IDs are not provided or incorrect. Ensure they are valid numeric values corresponding to existing resources.
- Assignee or Team not found: If the specified user or team ID does not exist or the authenticated user lacks permission, the assignment will fail.
- API authentication errors: Verify that the API key and base URL are correctly configured in the node credentials.
- Conflicting parameters: Providing both Assignee Id and Team Id will cause the Team Id to be ignored; ensure you provide only the intended assignee parameter.
Links and References
- ChatWoot API Documentation - Official API docs for reference on conversation assignment endpoints.