Integrations
RFF is built to sit next to the tools you already run, not replace all of them. Here’s what connects today, and what doesn’t yet, so you can plan around it.
Start free → · 100 endpoints · every integration on this page included
Your PSA (HaloPSA, ConnectWise, Autotask and friends)
- Alert emails a PSA can parse. Point an alert mailbox at your PSA’s inbound address. Each alert email links straight to the device and ends with a plain Device / Serial / Client / Alert / Status block, one “Label: value” per line, so the PSA’s email rules can map it to the right client and asset.
- One mailbox for every client. MSPs on the MSP plan set the PSA mailbox once, and alerts from every client Site route through it.
- Tickets that can close themselves. When the alert resolves, RFF sends a resolve event too, so a PSA rule can close the ticket the alert opened without anyone touching it.
- Ticket numbers on the alert. Record the PSA’s ticket number on the RFF alert (in the app, or through the API), so both sides point at each other.
Not yet: a native PSA connector that syncs devices into your PSA. If that’s what stands between you and a trial, tell me which PSA. It gets built for the first customer who needs it.
Webhooks
Every alert can go to a webhook URL as well as email: opens, and the resolve that follows. Use it for Teams or Slack channels, an on-call tool, or your own automation. There’s a Send a test event button next to the URL so you can see the payload before anything real fires.
REST API
A documented REST API on every plan, including Free: inventory, jobs, checks, alerts and devices. Keys are read-only or read-write, and every call is audited. Read more about the API.
Sign-in and user provisioning
- Sign in with Microsoft (Entra ID).
- SCIM 2.0 provisioning from Entra ID or Okta: your directory creates, updates and deactivates RFF users. Provisioned users arrive as viewers, so your directory decides who gets in and an RFF admin decides what they can do.
- Multi-factor authentication for everyone else.
Running alongside another RMM
You don’t have to rip anything out to try RFF. Push the RFF agent with your current RMM’s own script runner, run both side by side on a pilot group, and compare. RFF’s agent talks outbound on 443 only, so it needs no firewall changes to coexist.
Missing something? The integrations that get built next are the ones customers ask for. Send me a note, and say what you’d connect it to.