AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node interacts with the "System" resource of the AvantGuard NinjaOne API to retrieve user information. Specifically, the "Get Users" operation fetches a list of users from the system, optionally filtered by user type or including additional role information.

Common scenarios for this node include:

  • Retrieving all technician or end-user accounts in an IT management environment.
  • Fetching user details along with their roles for auditing or reporting purposes.
  • Integrating user data into workflows that automate user management or notifications.

Example use case: An IT admin wants to generate a report of all technicians currently registered in the system, including their assigned roles, to verify access levels.

Properties

Name Meaning
Additional Query Parameters Optional filters and flags to customize the user retrieval:
- User Type Filter users by type; options are "TECHNICIAN" or "END USER".
- Include Roles Boolean flag to include user role information in the response (true/false).

Output

The node outputs JSON data representing the list of users retrieved from the system. Each user object typically contains user details such as ID, name, email, and depending on the Include Roles flag, associated role information.

If binary data were involved (not indicated here), it would represent file attachments or similar content, but this node focuses on JSON user data only.

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.
  • Relies on the external AvantGuard NinjaOne service being accessible and responsive.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API keys.
    • Network errors if the API endpoint is unreachable.
    • Incorrect query parameter values causing empty or unexpected results.
  • Error messages:

    • Unauthorized or 401 errors: Verify the API key credential and permissions.
    • 400 Bad Request: Check that query parameters like userType are valid ("TECHNICIAN" or "END_USER").
    • Timeout or network errors: Ensure network connectivity and correct base URL configuration.

Links and References

Discussion