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 → Run Script On Device
AI-generatedOverview
This node allows you to run scripts or predefined actions on a specific device managed by the NinjaOne platform. It is useful for automating device management tasks such as executing maintenance scripts, running custom commands, or triggering built-in actions remotely on endpoints.
Typical use cases include:
- Running diagnostic or remediation scripts on devices.
- Triggering automated actions like software deployment or configuration changes.
- Passing parameters to customize script execution per device.
For example, you might use this node to run a security scan script on a group of devices or execute a built-in action to restart a service remotely.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number) specifying which device the script or action will run on. |
| Type | Specifies whether to run a built-in action (ACTION) or a custom script (SCRIPT). |
| Id | Script identifier (number) used when Type is SCRIPT to specify which script to run. |
| Uid | Built-in action identifier (string) used when Type is ACTION to specify the action. |
| Parameters | String containing parameters to pass to the action or script during execution. |
| Run As | Credential role or identifier under which the script/action should be executed. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to run the script or action on the specified device. The structure depends on the API response but generally includes status information about the execution request.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects a configured NinjaOne API credential in n8n to authenticate requests.
- Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
- Missing or invalid device ID: Ensure the device identifier is correct and the device exists in NinjaOne.
- Incorrect script or action identifiers: Verify that the script ID or built-in action UID matches those available in your NinjaOne environment.
- Authentication errors: Confirm that the NinjaOne API credentials are valid and have sufficient permissions.
- Empty or malformed parameters: If parameters are required by the script or action, ensure they are correctly formatted as strings.
- API request failures: Check network connectivity and NinjaOne API status if requests fail.
Common error messages typically relate to invalid IDs, unauthorized access, or missing parameters. Reviewing the NinjaOne API documentation and ensuring proper input values usually resolves these issues.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credentials Setup (for configuring NinjaOne API credentials)