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 integrates with the ChatWoot API to assign a conversation to either a specific user (assignee) or a team within an account. It is useful in customer support workflows where conversations need to be routed to the appropriate agent or team 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 should be assigned. |
| Team Id | The numeric ID of the team to which the conversation should be assigned. Ignored if Assignee Id is provided. |
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 assignment status. 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.
- The node 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 and Team Id conflict: If both Assignee Id and Team Id are provided, the node prioritizes Assignee Id and ignores Team Id. To assign to a team, omit the Assignee Id.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- API connectivity issues: Check network access to the ChatWoot instance URL and ensure it is reachable from n8n.