Skip to main content
The Confluence update blog post action updates an existing blog post in a Confluence space when you provide the blog post ID and the latest version information. Use it to revise titles, fix typos, or refresh content for announcements, launch notes, and other updates without managing Confluence APIs or authentication yourself. This write action supports workflows where agents keep a single canonical blog post up to date over time, instead of creating new posts for every change.

​
Limitations

  • Requires the latest version number. The update must include the current version number of the blog post and if the version number is out of date, the provider may reject the update.
  • In Confluence Cloud, blog posts do not follow a page hierarchy model. Parent page identifiers are typically not relevant for blog posts.
  • This action is subject to the same API limits and connector configuration you use for the Confluence (Cloud) data source, including any rate limits or exclusions for spaces, labels, or creators.

​
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 blog posts in the target space. Otherwise, the action fails with a permission error.

​
Supported parameters

ParameterTypeDescription
Body contentObjectRequired. Updated content body of the page, including representation and value, for example, storage format.
Post IDStringRequired. Unique identifier of the page to update.
Space IDStringRequired. Identifier of the space the page belongs to; used to validate or change the page’s space.
StatusStringStatus of the page after the update, for example, current, draft, or archived.
TitleStringRequired. Updated title of the page.
Version numberObjectRequired. Version object containing the new version number and related metadata for the update operation.
Minor editStringWhether this update is a minor edit.
Version messageStringOptional message describing the version update.

​
Usage example

You want to update a weekly product update blog post with new information and mark it as revised. Instruction to an agent: “Find the Confluence blog post titled Weekly product update — December 5 in the Engineering space. Update the title to add (Revised) and expand the Features section to include the new dashboard widgets feature. Mark this as a minor edit with the version message ‘Added dashboard widgets info’.” Resulting behavior:
  • Locates the existing blog post in the Engineering space and retrieves its current version number.
  • Calls the Update blog post action with:
    • Post ID set to the blog post ID.
    • Space ID set to the Engineering space ID.
    • Title updated to Weekly product update — December 5 (Revised).
    • Body content updated with the expanded Features section including dashboard widgets.
    • Version number set to the latest version to avoid conflicts.
    • Minor edit set to true to mark this as a small change.
    • Version message set to “Added dashboard widgets info” for tracking purposes.
Workflow tip: Always retrieve the current version number before updating to avoid version conflicts. The action automatically increments the version number when the update is successful.

​
Troubleshooting

  • Possible cause: The connected Confluence account does not have permission to edit blog posts in the target space.
  • Fix: Confirm that the account used for the Confluence connector has edit rights for the space and blog post, then retry the action.
  • Possible cause: The version.number provided is not the latest version for the blog post.
  • Fix: Retrieve the current version of the blog post, update version.number to that value, and retry.
  • Possible cause: The body object is missing required structure or content expected by the provider.
  • Fix: Ensure that body includes valid content in the expected format. When using agents, avoid overriding low-level body fields unless you have a specific need.
  • Possible cause: The underlying Confluence APIs are enforcing rate limits for your tenant.
  • Fix: Retry after a short delay. If the issue persists, your Glean admin may need to review connector-level rate-limit configuration or reduce concurrent write activity.

​
FAQs

No. The action expects the blog post to remain in its existing space. The Space ID parameter is used to validate that the blog post belongs to the specified space, not to move it.