Skip to main content
Complete Freshservice choice menus.
Freshservice routing and triage Procedures 1.5.0 offer the complete eligible synced menu. Missing policy descriptions no longer hide Groups, verified responders, or enabled field values. Selections outside the approved application policy retain decision evidence and request human review. Oversized menus explicitly refuse instead of truncating. Install compatible preparation 2.4.0 and publish a workflow revision to adopt the new behavior; existing published versions retain their pins.
Freshservice customer attribution uses stable department IDs.
Freshservice ingress can use the signed numeric workspace and department IDs to resolve an operator-reviewed Customer or internal-company binding before a workflow launches. Unknown, disabled, or invalid identities answer 422 without launching. The workflow receives the reviewed department label as companyName; the signed request body and HMAC contract remain unchanged.Platform operators manage bindings through the customers MCP group with getFreshserviceDepartmentBinding and putFreshserviceDepartmentBinding, backed by GET and PUT /api/v2/customers/freshservice-department-bindings. Changes use revision CAS and are audited. External Apps are refused; use a platform or Personal API key. Activation also requires a forge-mcp release containing the refreshed bundled operation catalog.PUT writes retain the existing confirmation or preauthorization requirements. Deploy the backend with PUT confirmation support before activating the refreshed MCP catalog.
Coordinated Freshservice triage policy.
Freshservice triage can use a reviewed policy release that supplies choosing guidance directly to Group and classification decisions while preserving complete eligible synced menus. The release coordinates the existing Priority policy and checks explicit Group/category requirements before preparing a ticket update. A conflicting dependency holds its related changes for review while independently supported fields remain eligible.Existing thresholds, technician selection and acknowledgments are preserved. Operators adopt the release through a new validated workflow revision; existing published versions retain their pins.
Organization knowledge ownership checkpoint.
The organization knowledge checkpoint moves the approved customer SOP inventory into each customer’s organization. All parts of a case move together, with its collection and version history preserved. The checkpoint refuses changed inventories or new file and draft dependencies, and runs once after signed triage attribution and production-manifest approval. Historical retrieval and audit records retain their original namespaces.
Organization knowledge move safeguards.
Organization knowledge moves now recover stale search partitions before moving ownership and commit search entries together with their owner. A changed destination, stale source, or conflicting destination collection stops the move before ownership changes. Existing production rollout approval requirements remain in effect.
RateLimit headers on every declared response.
The OpenAPI documents now declare RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset on every response of every operation. Until now they were left off every 401, a route’s own 429 and the shared 503, but those statuses carry them whenever the request spent from its bucket first:
  • an operation’s own 401, such as an External App’s user token that fails;
  • the general bucket’s 429 on an operation that also has a tighter limit of its own;
  • a 503 after the spend, such as a transient fault while the operation ran.
Nothing the API sends has changed. A refusal before the spend (a 401 from authentication, a stopped api_keys door’s 503 governance_door_stopped), a route’s own 429 and the limiter’s own 503 still carry none; the header descriptions say so. See rate limiting.