AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve client checklists associated with organizations. It allows users to fetch detailed checklist data filtered by various optional query parameters such as checklist IDs, organization IDs, checklist names, assigned user IDs, completion status, requirement status, and whether to include archived checklists.

Common scenarios for this node include:

  • Auditing or reviewing organizational checklists for compliance or operational purposes.
  • Automating reporting workflows that require checklist data from multiple organizations.
  • Filtering checklists based on assignment or completion status to track task progress.

For example, a user might use this node to get all incomplete required checklists assigned to a specific user across several organizations.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the checklist retrieval. Includes:
- Checklist Ids Comma-separated string of checklist IDs to filter results.
- Organization Ids Comma-separated string of organization IDs to limit the scope.
- Checklist Name Filter checklists by their name (string match).
- Assigned To User Id Numeric ID of the user to whom the checklist is assigned.
- Completed Boolean flag to filter checklists by completion status (true for completed, false otherwise).
- Required Boolean flag to filter checklists marked as required.
- Include Archived Boolean flag indicating whether to include archived checklists in the results.

Output

The node outputs JSON data representing the retrieved client checklists matching the specified filters. Each item in the output typically contains checklist details such as IDs, names, assignment info, completion status, and other metadata as provided by the NinjaOne API.

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 corresponding OpenAPI specification bundled internally.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Empty results: Verify that the query parameters are correct and correspond to existing checklists or organizations.
  • Invalid parameter types: For numeric fields like "Assigned To User Id," ensure numbers are provided, not strings.
  • Network issues: Confirm that the base URL is reachable and no firewall or proxy blocks the request.

Links and References

Discussion