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
Conversation Assignment → Assign A Conversation
AI-generatedOverview
This node operation assigns a conversation within an account to either a specific user (assignee) or a team. It is useful in customer support or communication platforms where conversations need to be routed to the appropriate handler for follow-up or resolution. For example, when a new customer inquiry arrives, this node can automatically assign the conversation to a particular support agent or a team responsible for that topic.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the 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 present. |
Output
The node outputs JSON data representing the result of the assignment operation. This typically includes details about the updated conversation, such as its new assignee or team assignment status. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node uses the ChatWoot REST API to perform the assignment action.
Troubleshooting
- Missing or invalid Account Id or Conversation Id: The node requires valid numeric IDs; ensure these are correctly set.
- Assignee or Team not found: If the provided assignee or team ID does not exist, the API may return an error.
- Authentication errors: Verify that the API key and base URL credentials are correctly configured.
- Conflicting parameters: Providing both Assignee Id and Team Id will cause the Team Id to be ignored; ensure this is intentional.
Links and References
- ChatWoot API Documentation (for understanding the conversation assignment endpoint)
- n8n documentation on creating custom nodes