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 Services
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about device services. Specifically, the "Get Device Services" operation fetches a list of services running on a specified device, optionally filtered by service name and state. This is useful for IT administrators or automation workflows that need to monitor, audit, or manage services on devices remotely.
Practical examples include:
- Automatically checking if critical services are running on a device.
- Filtering services by their current state (e.g., only running services).
- Integrating service status checks into broader incident response or maintenance workflows.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device whose services you want to retrieve. |
| Name | (Optional) Filter services by their exact service name. |
| State | (Optional) Filter services by their state. Possible values: UNKNOWN, STOPPED, START PENDING, RUNNING, STOP PENDING, PAUSE PENDING, PAUSED, CONTINUE PENDING |
Output
The node outputs an array of JSON objects representing the device services matching the query parameters. Each object corresponds to a service and contains details as returned by the NinjaOne API. The exact structure depends on the API response but typically includes service identifiers, names, states, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the user to configure the NinjaOne API credentials in n8n before use.
- Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
- Missing or invalid device Id: The "Id" property is required. Ensure it is set correctly; otherwise, the API call will fail.
- No services returned: If filtering by name or state yields no results, verify that the filters match existing services on the device.
- Authentication errors: Ensure the NinjaOne API credentials are valid and have sufficient permissions.
- Binary data errors: Not applicable for this operation.
- API request failures: Check network connectivity and NinjaOne API status.
Links and References
- NinjaOne API Documentation (general reference for endpoints and service data)
- n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)