Actions6
- User Actions
- Conversation Actions
- Team Actions
Conversation → Assign to Team
AI-generatedOverview
This node operation assigns a specific conversation to a team within the Msgboxx system. It is useful in scenarios where conversations need to be routed or managed by different teams, such as customer support or sales teams, to ensure proper handling and follow-up. For example, when a new customer inquiry comes in, this operation can assign the conversation to the appropriate team responsible for that type of inquiry.
Use Case Examples
- Assigning a conversation to the 'Support' team to handle a customer issue.
- Routing a sales inquiry conversation to the 'Sales' team for follow-up.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation to be assigned to a team. This must be a valid conversation ID string. |
| Team ID | The unique identifier of the team to which the conversation will be assigned. This ID is extracted from the Team resource response. |
Output
JSON
success- Indicates if the assignment operation was successful.actionTaken- Indicates that an action was performed on the conversation.type- The type of action performed, which is 'assignToTeam' in this case.conversationId- The ID of the conversation that was assigned.teamId- The ID of the team to which the conversation was assigned.message- A descriptive message confirming the assignment of the conversation to the team.
Dependencies
- An API key credential for authenticating requests to the Msgboxx Dev API at https://api.dev-env.msgbox.to
Troubleshooting
- Ensure the conversationId and teamId are valid and correctly extracted from previous API calls.
- Common errors may include invalid or missing IDs, resulting in failed API requests. Verify that the API key credential is correctly configured and has the necessary permissions.
- Check network connectivity and API endpoint availability if requests fail.
Links
- Msgboxx Dev API Documentation - Official API documentation for Msgboxx Dev environment, useful for understanding available endpoints and request formats.