RMM integration
N-able-stack MSPs get the same unified workspace — customers, devices, and notifications on one page alongside every other tool.
In Beta
Vectis + N-able N-central is in Beta. We built this connector against N-able N-central’s published API documentation (verified endpoints in scripts/audit/known-endpoints/n-able.json). It’s fully connectable today — credentials save and syncs run. Because N-able N-central doesn’t offer a public sandbox for us to live-test against, the first paying customer who connects it is the de-facto live validator. If you’re considering Vectis with N-able N-central and want to be the validator, talk to us.
What Vectis syncs
N-central customers map onto Vectis customer accounts on first sync, and from there Vectis pulls each device with its OS, hardware, last-seen, and agent version. Active notifications come in tagged by severity so the customer hub surfaces noise that matters — and rules can route N-central events into PSA boards the same way NinjaOne and Kaseya events already do.
What you can do
N-able N-central is a read-only adapter here — N-central's REST and GraphQL APIs document no verb to acknowledge or resolve a notification, so the lifecycle stays inside the N-central console. The value lands in cross-tool correlation: an N-central notification can fire a rule that opens a ConnectWise or HaloPSA ticket, mapped to the right customer, and lifecycle planning across the RMM fleet (warranty, refresh) doesn't care which RMM manages the endpoint.
Honest about the limits
Read-only adapter. N-central's REST and GraphQL APIs expose no documented verb to acknowledge or resolve a notification — the GraphQL surface exposes reads only on the notifications table, and the prior client's fabricated /api/notifications/{id}/acknowledge paths 404'd against any real tenant. The current client is documented against the verified endpoints in scripts/audit/known-endpoints/n-able.json. Vectis surfaces notifications on the customer hub and feeds them into rules; the ack/resolve lifecycle stays inside N-central.
How it correlates
N-able N-central on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
An N-central notification for a mapped customer triggers a rule that opens a ConnectWise or HaloPSA ticket on the right board. The PSA ticket carries the full alert body, mapped to the right customer, with no copy-paste.
N-central devices show up in the lifecycle pipeline with warranty + refresh status alongside NinjaOne + Kaseya devices. Refresh planning doesn't care which RMM manages the endpoint.
Setup snapshot
Generate an API token in N-central → Administration → API Access → Generate API Token, scoped to a read-only service role over customers, devices, and notifications. Vectis does not call any notification-mutation endpoints (N-central doesn't expose them). Paste the tenant URL and the token into Vectis and pick your N-able product — N-central today; N-sight and Take Control are planned follow-ups. Vectis tests with a GraphQL customers query before saving so a wrong-token configuration fails fast.
# In the Vectis hub, add the connector:
category RMM
vendor N-able N-central
status Read-onlyOther RMM integrations
Pricing
N-able N-central is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp
