NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

System → Get Activities

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve system activity logs based on various filters. It is designed to fetch detailed records of activities related to systems, devices, or users within an IT environment managed by NinjaOne. This can be useful for monitoring system events, auditing user actions, or tracking device-related activities.

Typical use cases include:

  • Auditing security-related events by filtering activities by type or status.
  • Monitoring device or system changes over a specific time range.
  • Fetching user-specific activity logs for compliance or troubleshooting.
  • Paginating through large sets of activity data using ID-based cursors.

Properties

Name Meaning
Class Filter activities by class: SYSTEM, DEVICE, USER, or ALL (default).
Before Return activities recorded before this date (ISO 8601 string).
After Return activities recorded after this date (ISO 8601 string).
Older Than Return activities with IDs older than this specified activity ID (number).
Newer Than Return activities with IDs newer than this specified activity ID (number).
Type Filter activities by a specific type (string).
Status Filter activities by one or more statuses (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) to narrow down activities to particular devices.
Page Size Limit the number of activities returned in one request (default 200).
Lang Language tag to localize the response (string).
Tz Time zone to adjust timestamps in the response (string).
Source Config Uid Direct the request to a specific script or source configuration (string).

Output

The node outputs an array of JSON objects representing the retrieved activities from the NinjaOne system. Each item in the output corresponds to one activity record as returned by the NinjaOne API. The structure of each activity object depends on the API response but typically includes details such as activity ID, timestamp, type, status, user involved, and related device or system information.

No binary data output is produced by this operation.

Dependencies

  • Requires an active NinjaOne API OAuth2 credential configured in n8n.
  • The node uses the NinjaOne API endpoint /v2/system/activities (implied by the resource and operation).
  • Proper API permissions are needed to access system activity logs.

Troubleshooting

  • No activities returned: Check that the filters (dates, class, type, etc.) are correctly set and that there are matching records in NinjaOne.
  • Authentication errors: Ensure the NinjaOne API OAuth2 credentials are valid and have not expired.
  • Invalid date format: The Before and After properties expect ISO 8601 date strings; incorrect formats may cause errors.
  • Rate limiting or API errors: NinjaOne API may limit requests; handle errors gracefully and consider adding retry logic.
  • Missing required parameters: Although most filters are optional, ensure that if you use ID-based pagination (Older Than, Newer Than), the values are valid numbers.

Links and References

Discussion