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 Automation Scripts
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve automation scripts from the system. It is designed to fetch available automation scripts, optionally filtered by language. This functionality is useful for users who want to integrate or automate tasks using predefined scripts managed within NinjaOne.
Practical examples include:
- Fetching all automation scripts in a specific language to display or process them further.
- Integrating automation scripts into workflows that require dynamic retrieval of script data based on language preferences.
Properties
| Name | Meaning |
|---|---|
| Lang | Language filter for the automation scripts. When specified, only scripts matching this language are retrieved. |
Output
The node outputs an array of JSON objects representing the automation scripts retrieved from the NinjaOne system. Each item in the output contains the full details of an automation script as returned by the NinjaOne API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for NinjaOne.
- The node uses the NinjaOne API endpoint
/v2/automation/scriptswith an optional query parameterlangto filter scripts by language. - Proper configuration of the NinjaOne OAuth2 credential in n8n is necessary for successful API requests.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Specifying an unsupported or incorrect language code may result in empty results.
- Network connectivity problems can prevent the node from reaching the NinjaOne API.
Error messages:
- Errors related to missing binary data do not apply here since this operation does not handle binary inputs.
- API errors will typically return messages from the NinjaOne service; ensure the OAuth2 token is valid and has sufficient permissions.
- If the node throws an error about failing to get input parameters, verify that the "Lang" property is correctly set or left empty if no filtering is desired.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring NinjaOne OAuth2 credentials)