AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to submit an integrity check job related to backups. It allows users to trigger a process that verifies the integrity of backup data, which is crucial for ensuring that backups are complete and uncorrupted. This operation is beneficial in scenarios where automated validation of backup health is required, such as in IT management workflows or scheduled maintenance tasks.

For example, an IT administrator could use this node to programmatically initiate integrity checks on backup devices or plans, helping to maintain data reliability without manual intervention.

Properties

Name Meaning
Additional Body Fields Optional fields to include in the request body when submitting the integrity check job. These include:
- Device Id: Numeric identifier of the device to check.
- Plan Uid: String identifier of the backup plan to check.

Output

The node outputs JSON data representing the response from the AvantGuard NinjaOne API after submitting the integrity check job. This typically includes details about the job submission status, identifiers, and any relevant metadata confirming that the job was accepted.

No binary data output is indicated.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will prevent successful authentication.
    • Providing invalid or missing Device Id or Plan Uid may cause the API to reject the request.
    • Network connectivity issues can lead to timeouts or failed requests.
  • Error Messages:

    • Authentication errors typically indicate problems with the API key or base URL configuration.
    • Validation errors from the API may specify which required fields are missing or malformed.
  • Resolution Tips:

    • Verify that the API key credential is correctly set up and has necessary permissions.
    • Ensure that Device Id and Plan Uid values correspond to existing resources in the NinjaOne system.
    • Check network settings and firewall rules to allow outbound connections to the API endpoint.

Links and References

Discussion