Actions6
- User Actions
- Conversation Actions
- Team Actions
Conversation → Assign to User
AI-generatedOverview
This node operation assigns a specific conversation to a user within the Msgboxx platform. It is useful in scenarios where conversations need to be delegated or managed by different users, such as customer support or team collaboration workflows. For example, after retrieving user IDs from the User resource, this operation can assign a conversation to a selected user by their user ID.
Use Case Examples
- Assigning a customer support conversation to a specific support agent by their user ID.
- Delegating a conversation to a team member responsible for follow-up.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to be assigned. This must be a valid conversation ID string. |
| User ID | The userId string extracted from the User resource response. This identifies the user to whom the conversation will be assigned. |
Output
JSON
success- Indicates whether the assignment operation was successful.actionTaken- Boolean flag indicating that an action was performed.type- The type of action performed, here it will be 'assignedToUser'.conversationId- The ID of the conversation that was assigned.userId- The ID of the user to whom the conversation was assigned.message- A descriptive message confirming the assignment.
Dependencies
- Requires an API key credential for the Msgboxx API to authenticate requests.
Troubleshooting
- Ensure the conversationId and userId are valid and exist in the Msgboxx system to avoid errors.
- Check API authentication credentials if requests fail due to authorization issues.
- Verify network connectivity to the Msgboxx API endpoint.
- Common error messages may include invalid ID errors or permission denied errors, which can be resolved by verifying input values and API permissions.
Links
- Msgboxx API Documentation - Official API documentation for Msgboxx, useful for understanding available endpoints and parameters.