Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
User → Get Many
AI-generatedSummary
Retrieve NinjaOne users, optionally filtering by user type and limiting the results or returning all pages. Each returned user is emitted as a separate n8n item.
Inputs
- Authentication (required) — Select OAuth2 (Authorization Code) or Client Credentials and configure the matching credentials.
- Return All — Off by default. When off, the node requests up to the Limit; when on, it fetches pages until no more results are returned.
- Limit — Maximum number of users to request when Return All is off; defaults to 50.
- Filters → User Type — Choose All, Technician, or End User. The default All selection omits the userType filter.
Output shape
A list of n8n items, one per user returned by NinjaOne.
Uses the NinjaOne users endpoint. Return All uses page-based requests; with Return All off, Limit is sent as pageSize. API errors are raised unless the node is configured to continue on fail.