MCP tool: get_team_routing_rules
Retrieves all routing rules configured for a specific team. These 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 retrieve routing rules for |
Response fields
Below are the fields you may see in each routing rule object in the response: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 |
Rule fields (andRules/orRules)
Each rule in theandRules
and orRules
arrays contains:
Field | Type | Description |
---|---|---|
field | string | Field to match against (e.g., “priority”, “status”) |
operator | string | Comparison operator (e.g., “EQUALS”, “CONTAINS”) |
value | string | Value to match against |
precedence | number | Rule precedence/priority |