4me

Enable the 4me connector in your fastn dashboard, then let each customer authenticate their own 4me account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no 4me client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own 4me 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.

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 request history and SLA state before proposing next steps.

fastn does. When 4me 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.

Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.

Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.

A common starting point: create and update service requests from your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding 4me does not change your per-connector cost. You can start free with 3 connected accounts.