NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Organization → Get Organization Devices

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve devices associated with a specific organization. It is designed to fetch paginated lists of devices, allowing users to specify the organization by its identifier and control pagination through page size and cursor parameters.

Common scenarios include:

  • Inventory management: Automatically retrieving all devices registered under an organization for asset tracking.
  • Monitoring setups: Fetching device lists to monitor status or perform bulk operations.
  • Reporting: Generating reports on devices within an organization.

Example use case:

  • A user wants to get the first 50 devices of organization ID 123 to display in a dashboard or trigger further workflows based on device data.

Properties

Name Meaning
Id Organization identifier (number). Specifies which organization's devices to retrieve.
Page Size Limit number of devices to return (number). Controls how many devices are fetched per call.
After Last Node ID from previous page (number). Used for pagination to continue fetching devices after this ID.

Output

The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the requested devices. The structure corresponds directly to the API's device list response, typically including device details such as IDs, names, statuses, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
  • The node uses the NinjaOne OAuth2 API credential for authorization.
  • No additional external dependencies beyond the NinjaOne API and n8n's HTTP request helpers.

Troubleshooting

  • Missing or invalid organization ID: Ensure the "Id" property is set correctly and corresponds to a valid organization in NinjaOne.
  • Pagination issues: If using "After" for pagination, verify that the value corresponds to a valid last node ID from the previous response.
  • API authentication errors: Confirm that the API key or OAuth2 credentials are properly configured and have sufficient permissions.
  • No devices returned: Could indicate the organization has no devices or incorrect filters; verify input parameters.
  • Binary data errors: Not applicable here since this operation does not handle binary data.

Common error messages:

  • Authentication failures: Check credentials.
  • 404 Not Found: Organization ID may be invalid.
  • 400 Bad Request: Invalid query parameters like pageSize or after.

Links and References

Discussion