IT Operations · Integration
Rootly
Add Rootly to your product for your customers, and give your AI agents governed access to it.
Rootly's API follows the JSON:API specification, so every payload nests attributes and relationships under a data envelope and pagination uses page number and size parameters, which means a client written for a flat REST shape needs rewriting. Incidents carry a kind, so test and scheduled incidents sit in the same collection as real ones and must be filtered out before any metrics you report are meaningful. Severities, teams, services, environments and functionalities are separate resources referenced by relationship, so resolving an incident's severity name costs an extra lookup unless you use the include parameter. Creating an incident can trigger the workflows that spin up a Slack channel and page the on-call rota, so an API write is rarely a quiet write. fastn holds each customer's Rootly token, keeps writes scoped to their own workspace, and handles upkeep as tokens rotate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Rootly workspace so incident data stays inside their tenant
Show live incident status and severity for the services a customer owns inside your own dashboard
Open a Rootly incident from an alert raised in your product, with the right service and severity attached
Report resolution times and post-incident follow-ups with test and scheduled incidents excluded
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent read incidents and on-call schedules to answer who is responsible right now, without paging anyone
Have an agent post timeline updates to an active incident while incident creation stays human-approved
Audit per tenant which incidents an agent read or updated and which workflows its writes triggered
Example prompt
Who is on call for the payments service in Rootly, and what open incidents are attached to it?
Set up Rootly in 4 steps
- 01Enable the Rootly connector from your fastn dashboard.
- 02Have each customer authorise their own Rootly 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 Rootly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Rootly integration without building it. Your customers connect their own Rootly 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 Rootly update is not your on-call problem.
- One integration serves your product and your agents. The same governed Rootly 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
Datadog
PagerDutyOften used alongside
Tools the same teams tend to run next to Rootly, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultRootly integration FAQ
How do I add a Rootly integration to my product?
Enable the Rootly connector in your fastn dashboard, then let each customer authenticate their own Rootly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Rootly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Rootly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Rootly 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 Rootly integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent read incidents and on-call schedules to answer who is responsible right now, without paging anyone
Who maintains the Rootly integration?
fastn does. When Rootly 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 Rootly 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 Rootly integration?
A common starting point: let a customer connect their own Rootly workspace so incident data stays inside their tenant. 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 Rootly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Rootly does not change your per-connector cost. You can start free with 3 connected accounts.
Add Rootly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.