NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Related Items → Get Related Items With Entity

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve related items associated with a specific entity type and ID. It is useful in scenarios where you need to fetch all items linked to an entity such as an organization, document, location, or technician within the NinjaOne platform. For example, you might want to get all attachments or checklists related to a particular organization or retrieve all knowledge base documents connected to a contact.

Properties

Name Meaning
Rel Entity Type The type of the related entity to query. Options include: ORGANIZATION, DOCUMENT, LOCATION, NODE, ATTACHMENT, TECHNICIAN, CREDENTIAL, CHECKLIST, END USER, CONTACT, KB DOCUMENT.
Rel Entity Id The unique numeric identifier of the related entity for which to fetch associated items.

Output

The node outputs an array of JSON objects representing the related items retrieved from the NinjaOne API. Each item corresponds to a related entity linked to the specified entity type and ID. The exact structure depends on the NinjaOne API response but generally includes details about each related item.

If binary data were involved (e.g., file uploads), it would be included in the output's binary property, but this operation only performs GET requests and returns JSON data.

Dependencies

  • Requires an active NinjaOne API OAuth2 credential configured in n8n.
  • The node uses the NinjaOne REST API endpoints to fetch data.
  • No additional environment variables are needed beyond the API authentication setup.

Troubleshooting

  • Missing or invalid credentials: Ensure that the NinjaOne API OAuth2 credential is correctly set up and authorized.
  • Invalid entity ID or type: Providing an incorrect or non-existent entity ID or type will result in empty results or API errors.
  • API rate limits or connectivity issues: Network problems or API rate limiting may cause request failures; retry or check network status.
  • No binary data errors: Not applicable here since this operation does not handle binary inputs.

Common error messages:

  • "No binary data exists on item!" or "No binary data property ..." — These do not apply to this operation but appear in other operations involving file uploads.
  • API error messages returned by NinjaOne will be passed through; verify the entity parameters and API access rights.

Links and References

Discussion