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
Organization → Get Organization Locations
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about an organization's locations. Specifically, the "Get Organization Locations" operation fetches all location data associated with a given organization identifier. This is useful in scenarios where you need to manage or analyze organizational structure, track assets or users by location, or integrate location-specific data into workflows.
Practical examples include:
- Automatically fetching and listing all office locations of a company for reporting.
- Integrating location data into IT asset management systems.
- Using location details to trigger location-based automation or alerts.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the organization whose locations you want to retrieve. This is a required input. |
Output
The node outputs JSON data containing the locations associated with the specified organization. The exact structure depends on the NinjaOne API response but typically includes details such as location names, addresses, identifiers, and possibly other metadata related to each location.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects a configured OAuth2 credential for authenticating requests to NinjaOne.
- Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
- Missing or invalid organization Id: Ensure that the "Id" property is set correctly and corresponds to an existing organization in NinjaOne.
- Authentication errors: Verify that the OAuth2 credentials are valid and have not expired.
- API request failures: Check network connectivity and NinjaOne service status.
- Error messages from the node: If the node throws an error, it will include the message returned by the NinjaOne API. Common issues include unauthorized access, resource not found, or malformed requests.
- To continue processing multiple items even if some fail, enable the "Continue On Fail" option in the node settings.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and responses)
- n8n OAuth2 Credential Setup