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 platform. It is useful in scenarios where conversations need to be routed or managed by different teams, such as customer support or sales teams. For example, when a new customer inquiry arrives, this operation can assign the conversation to the appropriate team responsible for handling that type of inquiry.
Use Case Examples
- Assigning a customer support conversation to the Support Team for resolution.
- 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. 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 whether the assignment operation was successful.actionTaken- Boolean flag indicating that an action was performed.type- The type of action performed, here it is 'assignToTeam'.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.
Dependencies
- Requires an API key credential for the Msgboxx API to authenticate requests.
Troubleshooting
- Ensure the conversationId and teamId are valid and exist in the Msgboxx system to avoid errors.
- Check that the API key credential is correctly configured and has the necessary permissions.
- If the assignment fails, verify network connectivity and the Msgboxx API status.
- Common error messages may include invalid ID errors or authentication failures; resolving these involves verifying input values and credentials.
Links
- Msgboxx API Documentation - Official API documentation for Msgboxx, useful for understanding endpoints and parameters.
