Confluence ADF

Change the requested parts of an existing Cloud page using its original atlas_doc_format body. Keep untouched nodes, attributes, marks, and page appearance. This workflow covers published pages with native ADF, not page creation, legacy-editor conversion, or Confluence Data Center.

Scope and source

• A request to edit or publish the specified page authorizes that change. A review or proposed edit ends with the proposal. Ask only when publication or its scope is not already authorized.
• Search tools and rendered, Markdown, or storage-format reads can help locate and understand a page. Use a direct ADF read as the editing baseline. A converted representation can flatten mentions or lose editor metadata even when its visible text looks correct.
• Use a write tool only when its contract supports the original ADF and version checks. The bundled helper uses REST v2 and checks appearance before and after the update. Do not rebuild a rich page from a search or converted tool response.
• Publishing the current version can merge into or overwrite an unpublished draft. Check for pending collaborative edits before publishing; resolve a divergent draft with its owner. The helper rejects an accessible divergent draft, but cannot lock drafts or appearance properties.