AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to manage Windows service configurations on remote devices. Specifically, the "Set Windows Service Configuration" operation allows users to update settings of a Windows service identified by its service ID on a specified device.

Common scenarios include automating service management tasks such as changing how and when a service starts (e.g., automatic start, delayed start, disabled) or updating the user account under which the service runs. This is useful for IT administrators who want to remotely configure services across multiple machines without manual intervention.

Example use cases:

  • Automatically setting critical services to start automatically after system boot.
  • Disabling unnecessary services to improve security or performance.
  • Changing the service logon account to comply with security policies.

Properties

Name Meaning
Id Numeric identifier of the target device where the Windows service configuration will be set.
Service Id String identifier of the specific Windows service to configure on the device.
Additional Body Fields Optional additional fields to customize the service configuration:
- Start Type Defines the service start mode. Options: AUTO START, AUTO START DELAYED, BOOT START, DEMAND START, DISABLED, SYSTEM START.
- User Name Username under which the service should run.

Output

The node outputs JSON data representing the response from the NinjaOne API after attempting to set the Windows service configuration. This typically includes confirmation of the updated service settings or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the AvantGuard NinjaOne API.
  • The node expects an API authentication token or key configured via n8n credentials to authorize requests.
  • Network access to the NinjaOne base URL must be available.

Troubleshooting

  • Invalid Device or Service Id: If the provided device or service identifiers are incorrect or do not exist, the API will return an error. Verify that the IDs correspond to valid entities in your NinjaOne environment.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key credential is correctly configured in n8n.
  • Invalid Start Type Values: Providing a start type outside the allowed options will result in request rejection. Use one of the predefined start types listed in the properties.
  • Network Issues: Connectivity problems to the NinjaOne API endpoint can cause timeouts or failures. Check network settings and firewall rules.

Links and References

Discussion