RMM integration
NinjaOne organizations, devices, and alerts mapped to the customer hub — and inline actions back into Ninja.
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 NinjaOne joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
A Ninja alert fires, a rule opens a PSA ticket, and Vectis links the two. When the ticket closes, a companion rule acks the Ninja alert. No more alerts that stay noisy long after the work is done.
Every Ninja device shows up on its mapped customer hub with warranty + age + health from the lifecycle module. Spot refresh candidates without a separate report.
Setup snapshot
In NinjaOne, go to Administration → Apps → API → Client App IDs and create a client-credentials application. Copy the Client ID and Client Secret (shown only once) into Vectis along with your region (us/eu/ca/oc — must match the URL you log into Ninja at). Vectis tests with /v2/organizations before saving. Webhooks are optional — when configured, alerts update in Vectis without waiting for the next poll.
Full setup guideavailable after signup
14-day free trial. Connect NinjaOne at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.