NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Related Items → Get Related Items With Host Entity Type

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve related items based on a specified host entity type. It is useful in scenarios where you want to fetch entities related to a particular type of resource within NinjaOne, such as organizations, documents, locations, nodes, checklists, or knowledge base documents. For example, you might use this node to get all documents related to a specific organization or all checklists associated with a certain location.

Properties

Name Meaning
Entity Type The type of the host entity for which related items are requested. Options include: ORGANIZATION, DOCUMENT, LOCATION, NODE, CHECKLIST, KB DOCUMENT

Output

The node outputs an array of JSON objects representing the related items retrieved from the NinjaOne API. Each item in the output corresponds to a related entity linked to the specified host entity type. The exact structure of each JSON object depends on the NinjaOne API response for related items.

No binary data output is indicated by the source code for this operation.

Dependencies

  • Requires an active NinjaOne API OAuth2 credential configured in n8n.
  • Depends on the NinjaOne API being accessible and the user having appropriate permissions to query related items.
  • Uses the NinjaOne API endpoint corresponding to the "Get Related Items With Host Entity Type" operation (exact endpoint URI is abstracted in the bundled code).

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Specifying an unsupported or incorrect entity type may result in empty responses or errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Errors returned from the NinjaOne API will be propagated as error messages in the node output if "Continue On Fail" is enabled.
    • If binary data is expected but missing (not applicable here), the node would throw an error indicating missing binary data.
  • Resolutions:

    • Verify that the NinjaOne API credentials are correctly set up and valid.
    • Ensure the entity type parameter matches one of the supported options.
    • Check network connectivity and API availability.

Links and References

Discussion