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 Active Jobs
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about active jobs in the system. Specifically, the "Get Active Jobs" operation under the "System" resource fetches a list of currently active jobs, optionally filtered by job type, device, language, or time zone.
Use cases include monitoring ongoing tasks within an IT management environment, auditing job statuses, or integrating job data into workflows for reporting or alerting purposes.
For example, you might use this node to:
- Retrieve all active backup jobs running on devices.
- Filter active jobs by language preference or time zone to localize reports.
- Track specific job types to trigger downstream automation when certain jobs are active.
Properties
| Name | Meaning |
|---|---|
| Job Type | Filter active jobs by their type (e.g., backup, scan). |
| Df | Filter active jobs by device identifier or name. |
| Lang | Language tag to filter or localize the job data returned. |
| Tz | Time zone to adjust or filter job timestamps accordingly. |
Output
The node outputs JSON data representing the list of active jobs matching the specified filters. Each item in the output array corresponds to one active job and includes details as provided by the NinjaOne API.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the NinjaOne API.
- The node uses HTTP requests with OAuth2 authentication to communicate with the NinjaOne service.
- No additional external dependencies beyond the NinjaOne API and n8n's built-in HTTP request capabilities.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid filter values (e.g., unknown job types or device identifiers) may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate misconfigured or expired API tokens; re-authenticate or update credentials.
- Validation errors from the API may occur if filter parameters are malformed; verify input values.
- If no active jobs are found, the output will be an empty array rather than an error.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of custom nodes and credentials)