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 → Control Windows Service
AI-generatedOverview
This node allows controlling Windows services on a specified device through the NinjaOne API. It supports actions such as starting, pausing, stopping, and restarting a Windows service identified by its service ID on a target device identified by its device ID.
Typical use cases include automating service management tasks across multiple devices in an IT environment, such as remotely restarting a critical service after deployment or stopping unnecessary services to free resources.
For example, an IT administrator can use this node to restart the "Print Spooler" service on a remote workstation after applying printer driver updates.
Properties
| Name | Meaning |
|---|---|
| Id | Numeric identifier of the target device where the Windows service is running. |
| Service Id | String identifier of the Windows service to control on the specified device. |
| Action | The operation to perform on the service. Options: START, PAUSE, STOP, RESTART. |
Output
The node outputs JSON data representing the response from the NinjaOne API after performing the requested action on the Windows service. This typically includes status information about the service control operation.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on proper configuration of the NinjaOne API credentials within n8n.
- Network access to the NinjaOne service endpoint is necessary.
Troubleshooting
Common issues:
- Invalid device or service identifiers may cause the API call to fail.
- Insufficient permissions or expired API tokens can result in authentication errors.
- Network connectivity problems may prevent communication with the NinjaOne API.
Error messages:
- Errors returned from the NinjaOne API will be included in the node's output if "Continue On Fail" is enabled.
- Typical error messages might indicate "Device not found", "Service not found", or "Unauthorized".
Resolutions:
- Verify that the device ID and service ID are correct and exist in the NinjaOne system.
- Ensure the API credentials are valid and have sufficient permissions.
- Check network connectivity and firewall settings.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and parameters)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials in n8n)