recipe-find-and-update-document

You can update an Umbraco document property by walking the content tree via CLI to locate the target node path, then using document get/update/publish calls with selective fields and JSON output to modify specific properties safely.

The safest way to publish Umbraco content changes is using a dry run for mutations before applying an explicit publish schedule payload, verifying modifications on stable IDs returned by API responses without risking accidental edits.

Yes, you can use CLI automation to find an Umbraco document without knowing its ID by walking the site tree path, such as "Home/Partners/Partner List", which returns the stable ID needed for subsequent updates.

Yes, the workflow supports targeted property updates by reading only the needed fields and updating specific properties, allowing you to change one or more values before triggering the publish action.

Path-based discovery relies on deterministic CLI calls using Umbraco tree walk and JSON output, meaning it requires an exact content tree path structure and may not work if the tree hierarchy is changed or ambiguous.

A dry run is required before publishing to validate mutations safely, ensuring the document update targets the correct stable IDs returned by the API and preventing accidental edits to the content tree.