NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Queries → Get Computer Systems

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve computer system data based on specified query parameters. It is designed to fetch paginated lists of computer systems, optionally filtered by device identifiers and monitoring timestamps. This functionality is useful for IT administrators or automation workflows that need to monitor or analyze computer system inventories and statuses within an organization.

Practical examples include:

  • Retrieving a list of all monitored computer systems with pagination support.
  • Filtering computer systems by specific device filters (e.g., device IDs or types).
  • Querying computer systems updated or monitored at a particular timestamp.

Properties

Name Meaning
Df Device filter: a string used to filter the computer systems by device criteria.
Ts Monitoring timestamp filter: a string representing a timestamp to filter monitoring data.
Cursor Cursor name: a string used for pagination to indicate the position in the result set.
Page Size Limit number of records per page: a number specifying how many records to return per page.

Output

The node outputs JSON data containing the response from the NinjaOne API for the "Get Computer Systems" query. The structure typically includes an array of computer system objects with their details as returned by the API. Pagination information may also be included depending on the API response.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured for authenticating with the NinjaOne API via OAuth2.
  • The node uses the NinjaOne API endpoint /v2/computer-systems (inferred from context) with GET requests.
  • No additional external dependencies beyond the NinjaOne API and n8n's HTTP request helper.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or OAuth2 token is correctly configured and has sufficient permissions.
  • Invalid query parameters: Passing incorrect values for filters like df, ts, or cursor may result in empty responses or errors. Validate parameter formats.
  • Pagination issues: If using cursor-based pagination, ensure the cursor value is correctly obtained from previous responses.
  • API rate limits: Frequent requests might hit NinjaOne API rate limits; handle errors gracefully and consider adding delays or retries.
  • Binary data errors: Not applicable here since this operation does not process binary data.

Common error messages will generally come from the NinjaOne API and should be interpreted according to their documentation, e.g., unauthorized access, bad request due to invalid parameters, or server errors.

Links and References

Discussion