NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Devices → Get Device Activities

AI-generated

Overview

This node operation fetches activity records related to a specific device from the NinjaOne platform. It allows users to retrieve detailed logs or events associated with a device, filtered by various criteria such as activity type, status, time range, and pagination controls.

Common scenarios where this node is beneficial include:

  • Monitoring device activities for security auditing.
  • Tracking changes or alerts generated by a device.
  • Integrating device event data into workflows for automated incident response or reporting.

For example, a user might use this node to get all recent alert activities of a particular device within a certain time zone and language preference, limiting the number of results returned per request.

Properties

Name Meaning
Id Device identifier (required).
Older Than Return activities recorded that are newer than the specified activity ID.
Newer Than Return activities recorded that are older than the specified activity ID.
Activity Type Return activities filtered by a specific type (string).
Status Return activities filtered by one or more statuses (string).
Series Uid Return activities related to a specific alert series (string).
Page Size Limit the number of activities to return (default 200).
Lang Language tag to localize the response (string).
Tz Time zone to adjust timestamps in the response (string).

Output

The output is an array of JSON objects representing device activities retrieved from the NinjaOne API. Each object contains details about a single activity record, including metadata such as activity type, status, timestamps, and any related alert or series identifiers.

If binary data were involved, it would be indicated here, but this operation returns only JSON data describing device activities.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node depends on the NinjaOne API endpoint /v2/devices/{id}/activities (implied from the context).
  • Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

  • Missing or invalid device ID: Ensure the "Id" property is set correctly and corresponds to an existing device in NinjaOne.
  • API authentication errors: Verify that the OAuth2 credential is valid and has sufficient permissions to access device activities.
  • Empty results: Check filter parameters like olderThan, newerThan, activityType, and status to ensure they match existing activity records.
  • Rate limits or API errors: NinjaOne API may enforce rate limits; handle errors gracefully and consider retry logic if needed.
  • Incorrect binary property name: Not applicable here since this operation does not process binary data.

Links and References

Discussion