Do you have an open API?

Internal REST API exists and powers the SPA. Public-facing versioned API with key management is queued for post-GA.

Do you support webhooks?

Outbound webhooks on ticket and invoice events are in design — flag if you need them during beta.

Will you build an integration to my favourite tool?

Maybe. We track aggregate demand from beta applications. The next integrations in the queue are migration tooling for the major incumbents.

What about Zapier / Make?

Once the public API ships, Zapier-style middlewares will work fine. We are not building a native Zapier connector pre-GA.

What we talk to

Integrations that actually flow.

We'd rather ship a handful of integrations where the data moves both ways than build a marketplace logo wall. Here's everything OpsMerge talks to today, and what's queued.

Apply for closed beta

Integrations

Short list. Deep work.

We'd rather ship five integrations that work than build a logo wall. Here's everything OpsMerge talks to today.

QuickBooks
Xero (soon)
Pax8
MSP360
Microsoft 365
CIPP
Proxmox
Dial 9
Companies House
Backblaze B2

Live in beta — billing & accounting

The money path, end to end

QuickBooks Online

Native OAuth. Push invoices from OpsMerge to QuickBooks with line items, customer references and per-line tax codes. UK VAT computed server-side from the tax codes — we never send hand-typed tax lines. HMAC-verified inbound webhooks materialise payments back into the OpsMerge ledger; a daily reconciliation worker catches anything the webhook drops. Per-realm token-bucket throttling honours Intuit's rate limits without surprise lockouts.

FreeAgent

Native OAuth, the same pattern as QuickBooks for MSPs who run their books in FreeAgent. Push invoices with line items and VAT-aware tax codes, pull payments back into the OpsMerge ledger, and a watermark-based sync keeps the two sides reconciled. Per-invoice push on demand or as part of the billing run.

Xero (coming soon)

On the roadmap: the same pattern as QuickBooks — native OAuth, invoice push with VAT-aware tax codes, payment pull and daily reconciliation — for MSPs who run their books in Xero. Not yet available.

Pax8

Delegation OAuth into your Pax8 reseller account. Reads cloud-licence subscriptions per customer, surfaces them as billable assets, uses the Pax8 history endpoint as the source of truth for proration. No-HMAC webhooks handled via signed-event polling fallback.

Companies House (UK)

Look up registered company names, numbers and addresses for your client records during onboarding and on the invoice branding card. Free Companies House API key required; the integration degrades gracefully to manual entry when no key is set.

Live in beta — RMM & operations

The platform path

Microsoft 365 (via CIPP)

Contact import from Entra (Azure AD) tenants for client matching. We integrate via CIPP rather than building direct Microsoft Graph wiring per MSP — your existing CIPP tenant handles the auth handshake, so the OpsMerge integration stays scoped to the data layer. Invite-based client portal login today; passwordless magic-link in design.

MSP360 Backup

Per-tenant credentials encrypted at rest using a CIPP-style envelope. Adaptive polling — hourly when backups are idle, ten-minute cadence when jobs are running. Hostname-based agent matching feeds backup status into the alerts pillar so a failed backup raises an alert exactly like any other monitoring signal.

Proxmox VE

API token-based hypervisor monitoring. Pulls VM inventory, status, host metrics. Hardened token privilege model with explicit ACLs. Roadmap moves the integration from --privsep=0 to a custom Proxmox role for tighter scope.

Dial 9 (telephony billing)

CSV CDR import for telephony billing pass-through. Synthesised record IDs, fast-path rating from the CSV cost field, append-to-invoice flow during the billing run. Per-tenant Dial 9 account credentials. The operator stays in control of the append step — no silent rate-table drift.

Backblaze B2 (object storage)

S3-compatible EU endpoint backing ticket attachments, agent artefacts and PDF invoices. Single shared bucket today; per-tenant key isolation on the post-GA roadmap.

A note on Stripe: we use it to bill MSPs for their OpsMerge subscription, nothing more. We do not insert Stripe between you and your customers, and your clients never see a Stripe checkout from OpsMerge. Your client billing flows through QuickBooks Online.

For our hosting, edge, object storage and mail-delivery sub-processors, see the Privacy Policy. We list them there as a single source of truth so it stays in sync with our DPA.

Live in beta — procurement & distribution

Distributor pricing, into your catalogue

Ingram Micro (Xvantage)

Reseller-API connection into Ingram Xvantage. Pull live distributor pricing and product data so hardware quotes are costed against what you'll actually pay, not a stale spreadsheet.

TD Synnex

Reseller-API connection for TD Synnex pricing and product lookup, feeding the same quoting and procurement path.

Exertis

Reseller-API connection for Exertis pricing and product data, on the same procurement flow as Ingram and TD Synnex.

Queued / in design

Next on the list

More UK distributors
Westcoast and Midwich next, with Stock in the Channel as a cross-distributor aggregator under research. (Ingram, TD Synnex and Exertis are already live above.)
Migration tooling
NinjaOne, Atera, SuperOps, HaloPSA — agent re-registration, ticket history import, asset CSV mapping.
Outbound webhooks
Generic webhook firing on ticket and invoice events.
Public REST API
Internal API exists; public-friendly versioning, key management and docs queued.
In-product documentation
Runbooks, network diagrams and KB articles overlaid on the asset register.
Slack / Teams
Outbound notifications. No full bidirectional bot pre-GA.
Mobile device management
Android in early-access beta: enrol devices, push passcode, encryption, app, Wi-Fi and update policies, and lock or wipe remotely. iOS to follow.

Posture

Why we don't have 200 logos

Most integrations marketplaces are 80% read-only OAuth handshakes nobody uses. We'd rather ship a dozen integrations that actually move data both ways than build a logo wall to make the buying page look busier.

If you need one that isn't listed, mention it on the beta application. Real demand drives the queue, not vendor-marketing budgets.

Common questions

Do you have an open API?
Internal REST API exists and powers the SPA. Public-facing versioned API with key management is queued for post-GA.
Do you support webhooks?
Outbound webhooks on ticket and invoice events are in design — flag if you need them during beta.
Will you build an integration to my favourite tool?
Maybe. We track aggregate demand from beta applications. The next integrations in the queue are migration tooling for the major incumbents.
What about Zapier / Make?
Once the public API ships, Zapier-style middlewares will work fine. We are not building a native Zapier connector pre-GA.

Missing an integration you'd actually use?

Tell us on the beta application. What tool, what flow, what volume. We prioritise by how many MSPs ask, not by who shouts loudest.