Configure Zoho CRM territory management rules via the API and assign accounts to territories based on criteria, then verify territory membership
domain: zoho.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET /crm/v8/settings/territories to list existing territory definitions and retrieve territory IDs
POST /crm/v8/settings/territories with a JSON body defining the territory name, parent territory ID (for hierarchy), and criteria rules (field conditions) that determine automatic assignment
Run the territory assignment by POST /crm/v8/Accounts/actions/run_territory_rule with the territory ID and optionally a list of record IDs to evaluate
GET /crm/v8/Accounts/{id}?fields=Territory_Name to confirm the territory field on individual account records reflects the assignment
Use GET /crm/v8/settings/territories/{territoryId}/accounts to list all accounts currently assigned to a territory
Known gotchas
Territory rule execution is asynchronous in Zoho CRM — the run_territory_rule endpoint returns a job ID and the assignments may not be reflected immediately on account records
Manually assigned territories (overrides) are not re-evaluated by automated rules unless the override is cleared first; the API does not warn when a rule evaluation is silently skipped due to a manual override
Territory management features are only available on Zoho CRM Enterprise and above; calling territory endpoints on lower-tier accounts returns a generic 'feature not supported' error
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?