Skip to content

Integrations

OpsMerge integrates with several third-party services that MSPs commonly use. All current integrations are included in your subscription — there's no "integrations tier".

Current integrations

IntegrationWhat it doesAuthDirection
Microsoft 365 (CIPP)User/mailbox/device/security data from client M365 tenantsYour CIPP instanceMostly read (write optional)
QuickBooks OnlinePush invoices and pull paymentsOAuthTwo-way
FreeAgentPush invoices and poll paid statusOAuthTwo-way
BitdefenderPull device + threat data from your BD tenantAPI keyRead-only
MSP360 BackupPull backup status from your MSP360 instanceAPI credentialsRead-only
Dial 9 (call billing)Import CDRs and rate calls against client contractsCSV / APIRead-only

Coming soon

  • Xero — two-way accounting sync (push invoices, pull payments), the same architecture as the QuickBooks Online integration. Not yet available.

What "integration" means in OpsMerge

A few patterns we follow consistently:

Bring your own tenant

For most integrations, you have an existing third-party tenant (your CIPP, your Bitdefender, your QBO realm). OpsMerge connects to yours — we don't resell or proxy.

This matters commercially: your existing licences keep working. It also matters operationally — if BD changes their API, your BD admin can talk to BD support directly; you don't need to wait for us to fix it.

Mostly read, sometimes write

We default to read-only: we pull data in, we don't push changes back. Write actions (suspend a user, change a backup plan, rotate a key) require an explicit opt-in per integration. Off by default to keep the default safe.

No vendor lock-in around your data

Anything we sync from an integration is exportable. If you stop using OpsMerge, you don't lose the data — your source-of-truth was the integration's own tenant anyway.

What's deliberately not on the integration list

  • Direct end-user identity providers for client portal login. We use magic links from your sending domain — see Brand setup.
  • Cloud cost management tools (Cloudability, Vantage, etc.). Not common enough among UK MSPs to prioritise yet.
  • Antivirus vendors other than Bitdefender (ThreatDown, Sophos, etc.). On the roadmap; talk to us if you specifically need one.

How to ask for a new integration

  1. Discord (#feature-requests) — propose, get votes.
  2. In-app feature request — gets recorded and surfaced to product.
  3. A note in a support ticket — counts as a request and routes to product.

We prioritise integrations by:

  • Number of MSPs asking (vote count + ticket frequency).
  • Quality of the third-party's API (some integrations are quick to build, others are months of work).
  • Strategic fit (whether it strengthens the unified MSP-operations story).

Common questions

"Can I integrate with X via a webhook?" For outbound notifications, OpsMerge can post alerts to Slack, Teams, and Discord webhooks (Settings → Notification Channels). For anything else — inbound or outbound — use the API.

"Can I run my own integration that nobody else uses?" Yes — call our API from your own code. Build it once, run it on your own infra (n8n, Zapier, custom service). That's what the API is there for. No need to wait for us to build a first-class integration if the third-party already speaks REST.

"Do integrations cost extra?" No. Every integration in this section is included in Ease In and Crack On.

Next

Browse a specific integration:

OpsMerge is a product of Brindleford Technologies Ltd, company number 16871436, registered in England and Wales.