Skip to main content
The Confluence Update page action modifies an existing Confluence page directly from an agent flow. Use it to update page content, titles, and metadata without creating a new page. This write action is typically used after a read action like Get pages or Get page by ID to fetch the current page, then modify and write the updated content back. This allows agents to keep existing documentation up to date.

​
Limitations

  • Large page bodies can be truncated when they pass through the model context window, when you fetch a long page and then append additional text before calling this action. In these cases, the updated page may contain only part of the original content.
  • The underlying body schema exposes multiple representations, for example, storage and wiki.
  • The action depends on the Confluence versioning model. If the version number you pass does not match with what Confluence expects, the update can fail without changing the page.

​
Prerequisites

  • Glean action must be enabled for your instance and the Confluence action pack must be available.
  • A connected Confluence account must exist for the user with permission to edit pages in the target space.

​
Supported parameters

ParameterTypeDescription
Body contentObjectRequired. Updated content body of the page, including representation and value, for example, storage format.
IDStringRequired. Unique identifier of the page to update.
Space IDStringIdentifier of the space the page belongs to; used to validate or change the page’s space if supported.
TitleStringRequired. Updated title of the page.
Version numberObjectRequired. Version object containing the new version number and related metadata for the update operation.
Body → wiki → representationStringThe representation format of the content. Supported values: ‘storage’, ‘atlas_doc_format’, ‘wiki’. Examples: “storage” “atlas_doc_format” “wiki”
Body → wiki → valueStringThe content body in the specified representation.
Content formatStringThe representation format of the content. Supported values: ‘storage’, ‘atlas_doc_format’, ‘wiki’. Examples: “storage” “atlas_doc_format” “wiki”
Version messageStringOptional version message describing the changes. Examples: “Updated content” “Fixed formatting”

​
Usage example

You want to update the API documentation page with new endpoint information. Instruction to an agent: “Find the REST API v3.0 Documentation page in the Engineering space and add a new section about the /users/batch endpoint. Include authentication requirements and rate limits. Add the version message ‘Added batch users endpoint documentation’.” Resulting behavior:
  • Calls Get pages to locate the REST API v3.0 Documentation page and retrieves its current version number.
  • Calls the Update page action with:
    • ID set to the page ID.
    • Space ID set to the Engineering space ID.
    • Title unchanged (REST API v3.0 Documentation).
    • Body content updated with the new endpoint section appended to existing content.
    • Version number set to the current version to avoid conflicts.
    • Version message set to “Added batch users endpoint documentation” for tracking purposes.
Workflow tip: Always fetch the current page content and version number before updating. This ensures you have the latest version and can append to existing content without losing information.

​
Troubleshooting

  • Possible cause: The action schema for the body field has changed, for example, around the storage representation, and the environment is using an outdated parsing or flattening configuration.
  • Fix: Confirm that your environment is on the latest action schema and parsing logic. If the failures persist, share the agent link and inputs with Glean support so they can verify the schema version.
  • Possible cause: A wiki body representation field such as body.wiki.representation is set without a corresponding body.wiki.value.
  • Fix: Clear all body.wiki.* fields in the action inputs and rely only on body.storage.* for content updates. Re-run the agent after removing wiki fields.
  • Possible cause: The model’s context window is too small to handle the full page body plus the new content, so the body is truncated before it is sent to the action.
  • Fix: Switch the agent or the specific update step to a model with a larger context window, and re-run the flow. If you still need to use a smaller context window, reduce the amount of page content you include in the prompt before calling the action.

​
FAQs

In most cases you should provide body content. Leaving the body empty can cause the request to fail or leave the page unchanged, depending on how the schema is interpreted in your environment.