IT Operations · Integration
Freshservice
Add Freshservice to your product for your customers, and give your AI agents governed access to it.
Freshservice is ITSM rather than a help desk with a different label, and the difference shows in what it stores. A ticket is one object among several: assets, changes and problems are first-class, and the useful integrations usually cross between them, because the question worth answering is which asset an incident touched and whether a change caused it. The instance lives at the customer's own subdomain, so there is no single host to point at, and a connector that assumes one will simply not resolve. Ticket fields and workflows are configured per instance, so mapping is configuration. fastn handles the subdomain, the credential and the field mapping per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Freshservice instance so IT tickets appear next to the workflow your product owns.
Read the asset behind an incident, which is the context that makes an IT ticket actionable.
Create or update a ticket from your product, with per-instance fields mapped as configuration.
React when a ticket or change moves state, rather than polling a busy service desk.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an incident with its affected assets before summarising impact.
An agent files or updates a ticket within governed permissions, with the write audited per tenant.
An agent checks whether a recent change touched the same asset as a new incident.
Example prompt
Which incidents this week touched the same asset, and was there a change before them?
Set up Freshservice in 4 steps
- 01Enable the Freshservice connector from your fastn dashboard.
- 02Have each customer authorise their own Freshservice account, so calls run under their credentials rather than a shared key.
- 03Decide which incidents, alerts and on-call schedules your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Freshservice integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Freshservice integration without building it. Your customers connect their own Freshservice account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Freshservice update is not your on-call problem.
- One integration serves your product and your agents. The same governed Freshservice connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
ServiceNow
PagerDutyWorks well with
JiraOften used alongside
Tools the same teams tend to run next to Freshservice, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultFreshservice integration FAQ
How do I add a Freshservice integration to my product?
Enable the Freshservice connector in your fastn dashboard, then let each customer authenticate their own Freshservice account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Freshservice client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Freshservice account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Freshservice account and only ever sees their own incidents, alerts and on-call schedules. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Freshservice integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads an incident with its affected assets before summarising impact.
Who maintains the Freshservice integration?
fastn does. When Freshservice changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How fast does a Freshservice alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the Freshservice integration?
A common starting point: let a customer connect their own Freshservice instance so IT tickets appear next to the workflow your product owns. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Freshservice integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Freshservice does not change your per-connector cost. You can start free with 3 connected accounts.
Add Freshservice to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.