NinjaOneInstall

Summary

Delete multiple asset relationships by specifying their IDs in a single request to the /v2/itam/asset-relationship endpoint.

Inputs

• id — JSON array of IDs of asset relationships to delete.
• customBody — Optional custom JSON object to send in the request body; merged with provided fields and takes priority.
• headerFilters — Optional custom HTTP headers to include in the request, specified as key-value pairs.
• queryFilters — Optional query-string filters to apply as name-value pairs.
• batching — Settings for batching input items into groups with delay intervals to control request flow.
• debug — Flag to include debug information about the actual request sent in the output.
• pagination — Pagination configuration, primarily for list operations but present as an option.
• timeout — Timeout in milliseconds to wait for server response before aborting the request.

Output shape

a single JSON object representing the API response to the deletion request

The response includes status or confirmation of deletion. Debug information is included if debug is true. Pagination settings do not affect this delete operation. Input batching causes multiple requests if multiple input items are provided.

Examples

Example 1: Delete asset relationships by specifying multiple IDs

Provide the IDs of asset relationships to delete in the 'Id' field as a JSON array, optionally include custom headers or query filters, then execute the node to perform the batch delete operation.

Links

• n8n community nodes installation guide