AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to manage device policies. Specifically, the "Reset Policy Overrides" operation under the "Management" resource allows users to reset any custom policy overrides applied to a particular device. This is useful in scenarios where an administrator wants to revert a device's policy settings back to their default state after temporary changes or troubleshooting.

Practical examples include:

  • Reverting security or configuration policies on a device that was temporarily modified.
  • Ensuring compliance by resetting unauthorized policy changes on managed devices.
  • Automating policy management workflows where devices need to be restored to baseline configurations.

Properties

Name Meaning
Id The unique identifier of the device for which the policy overrides should be reset. This is a required numeric value.

Output

The node outputs JSON data representing the result of the reset operation. Typically, this will include confirmation of success or details about the reset action performed on the specified device. The exact structure depends on the API response but generally confirms that the policy overrides have been cleared.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
  • Needs the base URL of the NinjaOne API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the provided OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Common issues:

    • Invalid or missing device ID: Ensure the device identifier is correct and exists in the NinjaOne system.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network or connectivity problems: Confirm that the base URL is reachable from the n8n environment.
  • Error messages:

    • Unauthorized or 401 errors typically indicate invalid credentials.
    • 404 errors may mean the device ID does not exist.
    • 400 errors could suggest malformed requests; double-check the input properties.

Resolving these usually involves verifying credentials, device IDs, and network access.

Links and References

Discussion