IT Operations · Integration
xMatters
Add xMatters to your product for your customers, and give your AI agents governed access to it.
xMatters pages people, but that is not what sets it apart. Its centre of gravity is the flow: a designer where an event arriving from a monitoring tool is enriched, filtered, routed and then pushed onward into a ticketing system, a chat channel or a deployment pipeline, with steps that call other tools rather than only notifying humans. An embedded xMatters integration triggers events into a customer's own flows, reads and updates alerts, looks up groups, shifts and who is genuinely on call, and reacts when a response comes back. That response is worth designing around. xMatters puts named choices in front of the person it reaches, so what returns is a decision rather than a bare acknowledgement, and your product can branch on it. Each customer's flows, groups and rotations belong to them. fastn holds the credentials per tenant and maintains the endpoints.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own xMatters instance so a condition your product detects enters the flow they already built for it.
Trigger an event carrying the properties a customer's flow expects, so enrichment and routing happen on their side rather than in your code.
Read groups, shifts and current on-call so your product can show who will actually be contacted.
Act on the response option a responder chose, so an approval or a hold given on a phone drives the next step in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which events fired overnight, who responded and what they chose.
An agent triggers or terminates an event within scoped permissions, with the flow it entered recorded.
An agent checks a group's shifts and any overrides before it names whoever is reachable right now.
Example prompt
What did responders choose on last night's xMatters events, and which are still awaiting a reply?
Set up xMatters in 4 steps
- 01Enable the xMatters connector in your fastn dashboard.
- 02Have each customer supply credentials for their own instance so events reach their people rather than yours.
- 03Agree the event properties their flows expect, map the response options you branch on, and enable the alert reads you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the xMatters integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an xMatters integration without building it. Your customers connect their own xMatters 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 an xMatters update is not your on-call problem.
- One integration serves your product and your agents. The same governed xMatters 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
PagerDuty
Opsgenie
SIGNL4Often used alongside
Tools the same teams tend to run next to xMatters, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultxMatters integration FAQ
How do I add an xMatters integration to my product?
Enable the xMatters connector in your fastn dashboard, then let each customer authenticate their own xMatters account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no xMatters client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own xMatters account?
Yes. Every connection is scoped to the individual customer, so each authorises their own xMatters 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 xMatters 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 reports which events fired overnight, who responded and what they chose.
Who maintains the xMatters integration?
fastn does. When xMatters 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 an xMatters 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 xMatters integration?
A common starting point: let each customer connect their own xMatters instance so a condition your product detects enters the flow they already built for it. 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 xMatters integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding xMatters does not change your per-connector cost. You can start free with 3 connected accounts.
Add xMatters to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.