Setup Overview
Setting up the Kaseya VSA X integration involves two main steps:Creating an API Token
Create a Third-Party Token in your VSA X portal with the scopes Neo Agent needs.
Connecting to Neo Agent
Configure the connection between your VSA X tenant and Neo Agent using your Token ID and Token Secret.
Prerequisites
Before starting the integration setup, ensure you have:- Admin Access: An account in your VSA X tenant with the API Access permission (Super Admin, or a custom role that includes it)
- Your tenant URL: e.g.
https://yourtenant.vsax.net
Kaseya VSA X (also written VSAX) is the modern, cloud-native Kaseya RMM built on the Pulseway engine — distinct from the classic VSA 9/10. Its REST API v3 lives at
https://<tenant>.vsax.net/api/v3.What Neo Can Do with VSA X
Neo Agent reads and (where you allow it) writes the VSA X REST API v3 surface, gated by per-area permission groups you configure in Agent Settings.Devices
Devices
- Device lookup — find devices, status, OS type, organization/site/group, applied policies, antivirus status
- Custom fields & notifications — read device custom fields and notifications
- Write — move a device to another group, update device custom fields
Assets (hardware & software inventory)
Assets (hardware & software inventory)
- Hardware inventory — BIOS, operating system, CPU, RAM, disks, network adapters
- Installed software — name, publisher, version per device
- Last-seen — the true
LastSeenOnlinetimestamp
The assets endpoint is rate-limited by Kaseya to 60 requests/hour, so Neo queries it sparingly.
Organizations, Sites, Groups
Organizations, Sites, Groups
- Hierarchy — read and (with write access) manage the organization → site → group structure and their custom fields
Automation
Automation
- Catalog — list automation scripts, tasks, and workflows and inspect execution history
- Execute — run pre-registered scripts on a device and read back the result (with write access to the Automation group)
Script execution runs scripts that already exist in your VSA X dashboard — Neo never submits ad-hoc source. To let Neo run on-prem PowerShell (AD / Exchange) through VSA X, register the Neo wrapper script — see On-prem AD & Exchange setup.
Patch, Protection, Notifications, System
Patch, Protection, Notifications, System
- Patch management — read patch policies and global rules
- Endpoint protection — read antivirus policies
- Notifications — read notifications; create notifications and manage webhooks (with write access)
- System — read audit logs, environment info, RBAC scopes, custom field definitions
Available Actions
| Category | Actions | Status |
|---|---|---|
| Devices | List/read devices, custom fields, applied policies, antivirus, notifications; move device; update custom fields | Available (read/write) |
| Assets | Read hardware + installed-software inventory (60 req/hr) | Available (read) |
| Organizations / Sites / Groups | Read and manage the tenant hierarchy | Available (read/write) |
| Automation | Browse scripts, tasks, workflows and execution history | Available (read) |
| Automation | Execute pre-registered scripts on devices and read results | Available (read/write) |
| Patch Management | Read patch policies and global rules | Available (read) |
| Endpoint Protection | Read antivirus policies | Available (read) |
| Notifications | Read notifications; create notifications and manage webhooks | Available (read/write) |
| System | Read audit logs, environment, scopes, custom field definitions | Available (read) |
Neo Agent uses the VSA X REST API v3. Make sure your Third-Party Token has the necessary permissions for the areas you want Neo to act in — see the API token guide.