Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node allows controlling Windows services on a specified device by sending commands such as start, stop, pause, or restart to the service. It is useful in IT management scenarios where automated control over Windows services is required, for example, restarting a critical service after an update or stopping a service before maintenance.
Practical examples:
- Automatically restarting a service that has stopped unexpectedly.
- Pausing a service temporarily during system diagnostics.
- Starting a service on a remote machine after deployment.
Properties
| Name | Meaning |
|---|---|
| Id | The identifier of the target device on which the Windows service runs (number). |
| Service Id | The identifier of the Windows service to be controlled (string). |
| Additional Body Fields | Optional additional fields; currently supports selecting the action to perform on the service: START, PAUSE, STOP, RESTART. |
Output
The node outputs JSON data representing the response from the service control API call. This typically includes status information about the requested action on the Windows service. There is no indication of binary data output.
Dependencies
- Requires an API key credential for authentication with the AvantGuard NinjaOne platform.
- Depends on the AvantGuard NinjaOne API endpoint configured via credentials.
- Uses the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
Common issues:
- Invalid device or service identifiers may cause the API to return errors indicating the resource was not found.
- Insufficient permissions or invalid API credentials will result in authentication errors.
- Network connectivity problems can prevent the node from reaching the API endpoint.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and valid.
- "Service not found" or similar: Verify that the provided service ID exists on the target device.
- "Device not found": Confirm the device ID is correct and accessible.
Resolving these usually involves verifying input parameters, ensuring proper credential setup, and confirming network access.
Links and References
- AvantGuard NinjaOne API Documentation (generic link, replace with actual if available)
- n8n documentation on Creating Custom Nodes