RMM integration
N-able-stack MSPs get the same unified workspace — customers, devices, and notifications on one page.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Actions Vectis can take
Write-back methods this adapter exposes. Rules can call them; so can inline actions on the customer hub. Every action is logged to the audit trail.
How it correlates
Vectis is about N-able N-central joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
An N-central notification for a mapped customer triggers a rule that opens a ConnectWise or HaloPSA ticket on the right board. When the ticket closes, a companion rule resolves the notification.
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. Use a service role with read on customers + devices + notifications and write on notifications (acknowledge + resolve). Paste the tenant URL + token into Vectis and pick your N-able product (N-central today; N-sight + Take Control are planned). Vectis tests with a GraphQL customers query before saving.
Full setup guideavailable after signup
14-day free trial. Connect N-able N-central at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.