AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node operation retrieves system activity logs from the AvantGuard NinjaOne platform. It allows users to query and filter activities recorded in the system, such as device events, user actions, or system-generated logs. This is useful for monitoring, auditing, and troubleshooting purposes within IT environments managed by NinjaOne.

Typical use cases include:

  • Fetching recent system or device activities to analyze security incidents.
  • Auditing user actions for compliance and operational oversight.
  • Filtering activities by date ranges, types, or statuses to generate reports or trigger workflows based on specific events.

Properties

Name Meaning
Additional Query Parameters Optional filters and parameters to refine the activities returned. Includes:
- Class Filter by activity class: SYSTEM, DEVICE, USER, or ALL (default).
- Before Return activities recorded before a specified date (ISO string).
- After Return activities recorded after a specified date (ISO string).
- Older Than Return activities with IDs older than the specified activity ID (number).
- Newer Than Return activities with IDs newer than the specified activity ID (number).
- Type Filter activities by type (string).
- Status Filter activities by status (string).
- User Filter activities related to specific user(s) (string).
- Series Uid Filter activities related to a specific alert series UID (string).
- Df Device filter (string).
- Page Size Limit the number of activities returned (number, default 200).
- Lang Language tag for localization (string).
- Tz Time zone for date/time filtering (string).
- Source Config Uid Direct request to a specific script via source config UID (string).

Output

The node outputs an array of activity objects in the json field. Each object represents a single activity record retrieved from the NinjaOne system, containing details such as timestamps, activity type, status, user information, and related metadata.

If binary data were involved (not indicated here), it would typically represent attachments or files related to activities, but this operation focuses on JSON-formatted activity logs.

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 uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Empty results: Check that the query parameters are correctly set and that there are activities matching the filters.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • Invalid date formats: Use ISO 8601 date strings for before and after parameters.
  • Rate limits or API errors: Verify API usage limits and handle errors gracefully in workflows.
  • Incorrect parameter names or values: Confirm that all additional query parameters conform to expected types and allowed values.

Links and References

Discussion