AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The node integrates with the AvantGuard NinjaOne API to retrieve backup job information. Specifically, the "Get Backup Jobs" operation under the "Backup" resource allows users to fetch a list of backup jobs with optional filtering and pagination. This is useful for IT administrators or automation workflows that need to monitor backup statuses, audit backup activities, or integrate backup data into reporting dashboards.

Practical examples include:

  • Automatically retrieving all recent backup jobs to verify successful backups.
  • Filtering backup jobs by device or status to identify failed or pending backups.
  • Paginating through large sets of backup jobs for batch processing or archival.

Properties

Name Meaning
Additional Query Parameters Optional filters and controls for the backup jobs query:
- Df (Device filter) Filter backup jobs by specific device identifier or name.
- Ddf (Deleted device filter) Filter backup jobs related to deleted devices.
- Sf (Backup job status filter) Filter backup jobs by their status (e.g., completed, failed).
- Ptf (Backup job planType filter) Filter backup jobs by their plan type.
- Stf (Backup job startTime filter) Filter backup jobs based on their start time.
- Include Which devices to include in results: active, deleted, or all. Default is "active".
- Cursor Cursor token for paginated requests to continue from a previous page.
- Page Size Limit the number of records returned per page. Default is 10000.

These parameters are sent as query parameters to the API endpoint to customize the retrieval of backup jobs.

Output

The node outputs JSON data representing the list of backup jobs retrieved from the API. The structure typically includes details such as job identifiers, device information, status, plan type, start times, and other metadata related to each backup job.

If the API supports pagination, the output may also include cursor tokens or paging information to allow fetching subsequent pages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request building and execution.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect filter values may result in empty responses or errors.
    • Large page sizes might lead to timeouts or performance issues.
  • Error messages:
    • Authentication errors usually indicate invalid API keys or misconfigured credentials.
    • Validation errors may occur if query parameters do not conform to expected formats.
  • Resolutions:
    • Verify API credentials and ensure they have necessary permissions.
    • Double-check filter parameter values for correctness.
    • Reduce page size if experiencing timeouts or slow responses.

Links and References

Discussion