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
Management → Get Installer
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve an agent installer for a specified organization and location. It allows users to request different types of installers (e.g., Windows MSI, Mac DMG, Linux DEB) tailored to their environment and usage needs. This is useful in scenarios where automated deployment or provisioning of NinjaOne agents is required across various operating systems and architectures.
Practical examples include:
- Automatically fetching the appropriate installer for a new device in a given location.
- Integrating installer retrieval into a larger automation workflow that provisions devices.
- Limiting the number of times an installer can be used by specifying a usage limit.
Properties
| Name | Meaning |
|---|---|
| Organization Id | Numeric identifier of the organization for which the installer is requested. |
| Location Id | Numeric identifier of the location within the organization where the installer will be used. |
| Installer Type | The type of agent installer to retrieve. Options: WINDOWS MSI, MAC DMG, MAC PKG, LINUX DEB, LINUX RPM, LINUX ARM 64 DEB, LINUX ARMV 7 A DEB, LINUX ARM 64 RPM, LINUX ARMV 7 A RPM. |
| Usage Limit | Numeric value specifying how many times the installer can be used. |
| Content | JSON object containing additional content parameters; by default includes "nodeRoleId": "auto". |
Output
The node outputs JSON data representing the response from the NinjaOne API call to get the installer. This typically includes metadata about the installer and possibly a download URL or binary data reference depending on the API's response format.
If the API returns binary data (e.g., the actual installer file), it would be handled as binary output, but this is not explicitly shown in the static code. The main output is a JSON object with the installer details.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for NinjaOne.
- Depends on the NinjaOne API being accessible and the user having permissions to request installers.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Missing or invalid organization or location IDs may cause the API to reject the request.
- Incorrect installer type selection could result in unsupported installer errors.
- If the usage limit is set improperly (e.g., negative numbers), the API might return validation errors.
- Network or authentication failures will prevent successful API calls.
Error messages:
- Errors returned from the NinjaOne API will be captured and can appear in the output JSON under an
errorfield if "Continue On Fail" is enabled. - Typical error resolution involves verifying input parameters, ensuring valid credentials, and checking network connectivity.
- Errors returned from the NinjaOne API will be captured and can appear in the output JSON under an
Links and References
- NinjaOne API Documentation (generic link, replace with actual if available)
- n8n documentation on OAuth2 Credentials
- n8n documentation on Creating Custom Nodes