NinjaOne icon

NinjaOne

Ninja One Public API documentation. <br><br>See also: <br> <a href="https://resources.ninjarmm.com/API/Ninja+RMM+Public+API+v2.0.5+Device+Filter+Syntax.pdf">Device Filter syntax</a><br><a href="https://app.ninjarmm.com/apidocs-beta/core-resources/articles/webhooks/overview">Webhooks</a>

Actions309

AssetTags → Merge existing tags

AI-generated

Summary

Merge multiple existing asset tags into one tag using NinjaOne's API, either by merging into an existing tag or creating a new tag to merge into.

Inputs

  • Tag Ids (required) — A JSON array of tag IDs to merge.
  • Merge Method (required) — Choose whether to merge into an existing tag or create a new tag for the merge.
  • Merge Into Tag Id — If merging into an existing tag, specify the target tag ID here.
  • Name — If creating a new tag, specify the new tag's name.
  • Description — If creating a new tag, optionally provide a description for the new tag.
  • Custom Body — Optionally provide additional JSON properties to include in the request body, which will override other fields.
  • Custom Headers — Add custom HTTP headers to be sent with the API request.
  • Query Filters — Add query-string parameters to the API request.
  • Batching Options — Configure batch size and interval for processing multiple items.
  • Debug — Enable to include detailed request info in the output for troubleshooting.
  • Pagination — Configure pagination behavior if applicable to the operation.
  • Timeout — Specify the request timeout in milliseconds.

Output shape

a single response object from the API confirming the merge operation result

The API request body is constructed from the fields provided, optionally overridden by customBody JSON. If merging into an existing tag, 'mergeIntoTagId' must be set; if creating a new tag, 'name' is required. Debug info is included in output if enabled.

Links

Discussion