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
Devices → Get Device Active Jobs
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve active jobs for a specified device. It is useful in IT management and monitoring scenarios where you need to track ongoing tasks or jobs running on devices managed by NinjaOne. For example, an IT administrator can use this node to fetch all active maintenance or deployment jobs currently assigned to a particular device, enabling real-time monitoring and automation of workflows based on job status.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number). Specifies which device's active jobs to retrieve. |
| Lang | Language tag (string). Optional parameter to specify the language for returned data. |
| Tz | Time Zone (string). Optional parameter to specify the time zone context for date/time fields in the response. |
Output
The node outputs JSON data containing the list of active jobs for the specified device. The structure corresponds to the NinjaOne API response for active jobs on a device, typically including details such as job IDs, statuses, start times, and other relevant metadata about each active job.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for NinjaOne.
- The node uses NinjaOne's REST API endpoints to fetch data.
- Proper network access to NinjaOne API endpoints is necessary.
Troubleshooting
- Missing or invalid device ID: Ensure the "Id" property is set correctly and corresponds to an existing device in NinjaOne.
- Authentication errors: Verify that the OAuth2 credential is valid and has sufficient permissions to access device job information.
- Empty or unexpected responses: Check if the device actually has active jobs; otherwise, the response may be empty.
- Network issues: Confirm connectivity to the NinjaOne API endpoint.
- Error messages from API: These will be surfaced in the node output if "Continue On Fail" is enabled; otherwise, they will cause the workflow to error out. Common errors include unauthorized access, resource not found, or rate limiting.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring API authentication)