MCP tool: create_team_routing_rule
Creates a new routing rule for a specific team. Routing rules determine how tickets are automatically assigned and routed within the team based on various conditions and criteria.
Example prompt
Input parameters
| Name | Type | Required | Description |
|---|---|---|---|
| teamId | string | Yes | The ID of the team to create a routing rule for |
| name | string | Yes | The name of the routing rule group |
| resultTeamId | string | Yes | The ID of the team that tickets will be routed to |
| description | string | No | The description of the routing rule group |
| evaluationOrder | number | No | The order in which this rule should be evaluated |
| andRules | string[] | No | Rules that must all match (AND condition) |
| orRules | string[] | No | Rules where any match is sufficient (OR condition) |
Response fields
The response will contain the created routing rule with the same structure as theget_team_routing_rules tool:
| Field | Type | Description |
|---|---|---|
| id | string | Routing rule unique ID |
| name | string | Routing rule name |
| description | string | Routing rule description |
| teamId | string | Team ID this rule belongs to |
| evaluationOrder | number | Priority/order for rule evaluation |
| resultTeamId | string | Target team ID for routing |
| fallbackTeamId | string | Fallback team ID if primary routing fails |
| andRules | array | Array of AND conditions (all must match) |
| orRules | array | Array of OR conditions (any can match) |
| createdBy | string | Name of user who created the rule |
| createdById | string | ID of user who created the rule |
| createdAt | string (ISO8601) | Creation timestamp |
| updatedAt | string (ISO8601) | Last update timestamp |