Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
System → Get Locations
AI-generatedOverview
This node integrates with the NinjaOne API to retrieve system-related data. Specifically, the "Get Locations" operation under the "System" resource fetches a list of locations managed within NinjaOne. This is useful for workflows that need to organize or filter assets, devices, or policies by their physical or logical location.
Practical examples include:
- Automating asset management by syncing location data into an external database.
- Filtering alerts or tickets based on device locations.
- Generating reports segmented by location.
Properties
| Name | Meaning |
|---|---|
| Page Size | Limit number of locations to return. If set to 0, it may return all available locations. |
| After | Last Location Identifier from previous page, used for pagination to get the next set. |
Output
The node outputs an array of JSON objects, each representing a location retrieved from the NinjaOne API. The exact structure depends on the API response but typically includes fields such as location ID, name, and other metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for NinjaOne.
- The node uses NinjaOne's REST API endpoints to fetch data.
- No additional environment variables are explicitly required beyond the API credential setup.
Troubleshooting
Common issues:
- Pagination parameters (
Page SizeandAfter) not set correctly may result in incomplete data retrieval. - Missing or invalid API credentials will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
- Pagination parameters (
Error messages:
- Errors related to missing binary data do not apply here since this operation does not handle binary inputs.
- Authentication errors will indicate invalid or expired tokens; re-authenticate the NinjaOne API credential.
- API rate limits or server errors will be returned from the NinjaOne API and surfaced as error messages.
Links and References
- NinjaOne API Documentation (general reference): https://api.ninjaone.com/docs
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/