AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The node integrates with the AvantGuard NinjaOne API to retrieve reports on Windows services. Specifically, the "Get Windows Services Report" operation fetches detailed information about Windows services running on devices managed by NinjaOne. This is useful for IT administrators and support teams who want to monitor service states across their infrastructure, troubleshoot issues, or generate compliance and operational reports.

Practical examples include:

  • Listing all running or stopped services on a set of devices.
  • Filtering services by name or state to identify problematic or critical services.
  • Paginating through large sets of service data using cursors and page size parameters.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination controls for the query:
- Df Device filter: specify device(s) to limit the report scope.
- Name Service name: filter results to services matching this name.
- State Service state: filter by service status. Options: UNKNOWN, STOPPED, START PENDING, RUNNING, STOP PENDING, PAUSE PENDING, PAUSED, CONTINUE PENDING.
- Cursor Cursor name: used for paginating through large result sets.
- Page Size Limit number of records per page (default 1000).

These parameters are passed as query parameters in the API request to refine and control the returned data.

Output

The node outputs JSON data representing the Windows services report retrieved from the NinjaOne API. The structure typically includes an array of service objects, each containing details such as service name, state, device association, and other metadata provided by the API.

If the API supports pagination, the output may also include cursor information to fetch 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.
  • Relies on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Invalid query parameters: Verify that filter values like service state match one of the allowed options.
  • Pagination issues: If using cursors, ensure the cursor value is valid and not expired.
  • Empty results: Check that device filters and service names are correct; no matches will return empty arrays.
  • API connectivity: Confirm network access to the NinjaOne API endpoint and that the base URL is correct.

Links and References

Discussion