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 → Request Scripting Options
AI-generatedOverview
This node interacts with the NinjaOne API, specifically supporting various management-related operations. For the Management resource and the Request Scripting Options operation, it retrieves scripting options available for a specified device. This is useful in scenarios where you want to dynamically fetch or update scripts that can be run on devices managed by NinjaOne.
Practical examples include:
- Fetching available scripting options for a device before running automation tasks.
- Integrating device-specific script retrieval into an automated workflow for patch management or configuration enforcement.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number). Specifies which device's scripting options to request. |
| Lang | Language (string). Optional query parameter to specify the language for the scripting options. |
Output
The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the requested scripting options. The exact structure depends on the API response but generally includes details about available scripts or scripting configurations for the specified device.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
- Uses the NinjaOne OAuth2 API credential for authenticated HTTP requests.
- Relies on the NinjaOne API endpoint
/v2/...to fetch scripting options.
Troubleshooting
- Missing or invalid device Id: Ensure the "Id" property is set correctly as a number; otherwise, the API call will fail.
- Authentication errors: Verify that the API key or OAuth2 credentials are valid and have sufficient permissions.
- No binary data error: Not applicable here since this operation does not handle binary data.
- API request failures: Check network connectivity and NinjaOne API status if requests time out or return errors.
- Continue on Fail: If enabled, errors per item will be returned in the output JSON under an
errorfield instead of stopping execution.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and parameters)
- n8n Documentation - Creating Nodes