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

KnowledgeBaseArticles → Move knowledge base items

AI-generated

Summary

Move specified knowledge base folders and/or documents to a different folder and optionally to another organization within NinjaOne.

Inputs

  • folderIds — An array of folder IDs representing the knowledge base folders to move.
  • documentIds — An array of document IDs representing the knowledge base documents to move.
  • destinationFolderId — The ID of the folder to which the specified folders and documents will be moved.
  • destinationOrganizationId — The ID of the destination organization (client). Use this if the root folder of the client does not exist.
  • customBody — Optional JSON object to send arbitrary fields in the request body. Custom fields override other fields.
  • headerFilters — Optional custom HTTP headers to include in the API request.
  • queryFilters — Optional query parameters to include in the API request.
  • batching — Optional settings to batch input items for multiple requests, including batch size and interval between batches.
  • debug — If enabled, includes the full request details in output for troubleshooting.
  • pagination — Pagination settings for list operations (not typically applicable to this move operation).
  • timeout — Time in milliseconds to wait for the server to respond before aborting the request.

Output shape

a single JSON object representing the API response confirming the move operation

The response structure depends on the NinjaOne API. The node sends a PATCH request to /v2/knowledgebase/folders/move with merged body fields. Custom body values take precedence over other inputs. Debug output includes full request details if enabled.

Links

Discussion