Actions64
- Website Actions
- Conversation Actions
- People Actions
- Operator Actions
- Settings Actions
- Analytics Actions
- Availability Actions
- Campaign Actions
- Helpdesk Actions
- Visitors Actions
- Batch Actions
- Verify Actions
Conversation → Assign Routing
AI-generatedOverview
This node operation assigns routing for a conversation in the Crisp platform. It allows you to assign a conversation to a specific user by their user ID, which is useful for directing conversations to the appropriate operator or agent for handling.
Use Case Examples
- Assign a conversation to a specific support agent by providing the website ID, session ID of the conversation, and the user ID of the agent to route the conversation to.
- Use this operation to automate conversation assignment in a customer support workflow, ensuring that conversations are handled by the right team member.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the website associated with the conversation. |
| Session ID | The session ID of the conversation to which routing will be assigned. |
| Additional Fields | Optional fields for assigning routing, including 'Assign to User ID' which specifies the user ID to assign the conversation to. |
Output
JSON
assignuser_id- The user ID to which the conversation routing is assigned
Dependencies
- Crisp API key credential
Troubleshooting
- Ensure the Website ID and Session ID are correct and correspond to existing entities in Crisp.
- Verify that the 'Assign to User ID' is valid and corresponds to an active user in the Crisp system.
- Check API credentials and permissions to ensure the node can perform routing assignments.
- Common errors may include authorization failures, invalid session IDs, or missing required fields. Verify all inputs and credentials are correct.