AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The "Get Device Activities" operation retrieves a list of activities related to a specific device identified by its ID. This node is useful for monitoring and auditing device events, tracking status changes, or analyzing activity logs over time. For example, it can be used to fetch recent alerts, status updates, or other recorded actions on a device in an IT management or security context.

Properties

Name Meaning
Id The unique identifier of the device whose activities you want to retrieve.
Additional Query Parameters Optional filters and controls for the query:
- Older Than Return activities recorded that are newer than the specified activity ID (pagination/filtering).
- Newer Than Return activities recorded that are older than the specified activity ID (pagination/filtering).
- Activity Type Filter activities by their type (e.g., alert, status update).
- Status Filter activities by their status or statuses.
- Series Uid Filter activities related to a specific alert series.
- Page Size Limit the number of activities returned (default 200).
- Lang Language tag to localize returned data if supported.
- Tz Time zone to adjust timestamps in the response.

Output

The output JSON contains an array of activity objects related to the specified device. Each activity typically includes details such as activity ID, type, status, timestamp, and any associated metadata like alert series or localized information depending on the query parameters. The node does not output binary data.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard NinjaOne service.
  • Needs the base URL of the API configured in credentials.
  • Depends on the external AvantGuard NinjaOne API endpoint to fetch device activities.

Troubleshooting

  • Common issues:
    • Invalid or missing device ID will result in errors or empty results.
    • Incorrect or expired API credentials will cause authentication failures.
    • Using incompatible or unsupported query parameters may lead to unexpected responses or errors.
  • Error messages:
    • Authentication errors indicate problems with the API key or token; verify and update credentials.
    • "Device not found" or similar errors suggest the provided device ID does not exist or is inaccessible.
    • Rate limiting or timeout errors require retrying after some delay or checking network connectivity.

Links and References

Discussion