NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Related Items → Create Related Item

AI-generated

Overview

This node integrates with the NinjaOne API to create a related item linked to an entity within the NinjaOne platform. It allows users to specify the type of entity (such as an organization, document, location, node, checklist, or knowledge base document) and the specific entity ID to which the related item should be attached.

Common scenarios include automating the association of various resources or documents to entities managed in NinjaOne, such as linking a checklist to a particular organization or attaching a document to a node. This can streamline workflows that require maintaining relationships between different types of data within NinjaOne.

Example use case: Automatically creating a related document for a specific organization after a certain event occurs, ensuring all relevant information is connected and easily accessible.

Properties

Name Meaning
Entity Type The type of entity to which the related item will be linked. Options: ORGANIZATION, DOCUMENT, LOCATION, NODE, CHECKLIST, KB DOCUMENT
Entity Id The unique identifier (numeric) of the entity instance to which the related item will be created

Output

The node outputs JSON data representing the response from the NinjaOne API after creating the related item. This typically includes details about the newly created related item, such as its identifiers and any metadata returned by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node depends on proper configuration of the NinjaOne API credentials within n8n.
  • Network access to the NinjaOne API endpoint is necessary.

Troubleshooting

  • Missing or invalid Entity Id: Ensure the Entity Id is a valid number corresponding to an existing entity in NinjaOne.
  • Invalid Entity Type: Confirm that the Entity Type selected matches one of the supported options.
  • Authentication errors: Verify that the NinjaOne API credentials are correctly configured and have sufficient permissions.
  • API request failures: Check network connectivity and NinjaOne API status if requests fail.
  • Binary data errors: Not applicable for this operation, but other operations in the node may require binary input.

If the node throws an error indicating missing parameters, verify that all required properties are set before execution.

Links and References

Discussion