AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve antivirus status reports. Specifically, the "Get Antivirus Status Report" operation under the "Queries" resource allows users to fetch detailed information about antivirus product states across devices monitored by NinjaOne.

Typical use cases include:

Monitoring antivirus deployment and health across an organization's endpoints.
Generating reports for security audits or compliance checks.
Automating alerts or workflows based on antivirus status changes.

For example, a user might configure this node to pull the latest antivirus status filtered by a specific device or product name, then use the data to trigger notifications if any endpoint shows an outdated or disabled antivirus product.

Properties

Name	Meaning
Additional Query Parameters	Optional filters and pagination controls to refine the antivirus status report query. Includes: • Df: Device filter (string) • Ts: Monitoring timestamp filter (string) • Product State: Filter by antivirus product state (string) • Product Name: Filter by antivirus product name (string) • Cursor: Cursor for paginated results (string) • Page Size: Limit number of records per page (number)

Name

Meaning

Additional Query Parameters

Optional filters and pagination controls to refine the antivirus status report query. Includes:
• Df: Device filter (string)
• Ts: Monitoring timestamp filter (string)
• Product State: Filter by antivirus product state (string)
• Product Name: Filter by antivirus product name (string)
• Cursor: Cursor for paginated results (string)
• Page Size: Limit number of records per page (number)

These parameters allow precise control over which antivirus status records are retrieved, supporting efficient data handling and targeted queries.

Output

The node outputs JSON data representing the antivirus status report as returned by the NinjaOne API. This typically includes details such as device identifiers, antivirus product names, their current states, timestamps, and possibly pagination cursors if the result set is large.

No binary data output is indicated for this operation.

Dependencies

Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
The node uses the base URL provided in the credentials to make HTTP requests.
No additional external dependencies beyond the NinjaOne API and its authentication are required.

Troubleshooting

Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
Invalid query parameters: Verify that filters like device name, product state, or timestamps are correctly formatted and valid according to NinjaOne API specifications.
Pagination issues: When using cursor and page size, ensure proper handling of paginated responses to avoid missing data.
Network or API downtime: Check network connectivity and NinjaOne service status if requests fail unexpectedly.

Common error messages will likely relate to HTTP status codes such as 401 Unauthorized (authentication failure), 400 Bad Request (invalid parameters), or 500 Internal Server Error (API issues). Resolving these involves checking credentials, input parameters, and retrying after some time.

Links and References

AvantGuard NinjaOne API Documentation (for detailed API usage and parameter definitions)
n8n Documentation (for general guidance on using API nodes and handling pagination)