Reference · built on requestConnectorFiles, documents & spreadsheets

Confluence

Spaces, pages, blog posts, attachments, and comments from Confluence Cloud through its v2 REST API.

Request accessPricing ↗

About

Confluence Cloud is Atlassian's wiki. Teams write pages and blog posts inside spaces, attach files, comment inline or at the foot of a page, and keep a version record of every edit. The v2 REST API exposes each of those objects with cursor pagination, and a Connect app can subscribe to page, attachment, comment, and space events.

Through Fibric, an operator reads the pages your team relies on, notices when they go stale or when nothing covers a recurring question, and proposes a draft page or a comment. You approve each one. The connector writes the page or comment once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Confluence and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Pages in a space through GET /spaces/{id}/pages and GET /pages, with status current or draft and a version record
  • Page body in storage or atlas_doc_format from GET /pages/{id}
  • Blog posts through GET /blogposts and GET /spaces/{id}/blogposts
  • Attachments on a page through GET /pages/{id}/attachments, with thumbnail download
  • Footer and inline comments on pages and blog posts, with reply threads through /footer-comments/{id}/children
  • Connect webhook events such as page_created, page_updated, page_trashed, attachment_created, and space_created
  • Rate-limit state from X-RateLimit-Remaining and X-RateLimit-NearLimit on every response

Proposed actions

  • Target capability: propose a new page through POST /pages, in storage or atlas_doc_format, as a draft or published
  • Target capability: propose a page update through PUT /pages/{id}, carrying the next version number
  • Target capability: propose a footer comment on a page through POST /footer-comments
  • Target capability: propose a blog post through POST /blogposts in a chosen space
  • Target capability: propose a title change through PUT /pages/{id}/title

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Find the article support keeps rewriting

    The operator compares questions agents answer by hand against pages in your support space. When no page covers the question, it proposes a draft page through POST /pages for your review.

    With Knowledge Gap

  • Keep saved replies aligned with the source page

    When a policy page changes, a page_updated event fires. The operator finds saved replies that quote the old text and proposes updated wording. You approve each one.

    With Macro Match

  • Onboarding checklist that reads the real handbook

    The operator pulls the current version of onboarding pages and proposes a checklist per new hire, with a footer comment on the page when a step has gone stale.

    With Onboarding Checklist

  • Evidence from the page history

    The operator collects the version record and attachments of policy pages into an evidence packet, with links back to each page and version.

    With Compliance Evidence

Requirements

  • A Confluence Cloud site; requests go to https://api.atlassian.com/ex/confluence/{cloudid}/ once the cloudid is read from accessible-resources
  • An OAuth 2.0 (3LO) app with read:page:confluence, read:attachment:confluence, read:comment:confluence, and write:page:confluence scopes
  • offline_access in the scope so the app receives a refresh token
  • A Connect app descriptor if you want webhook events instead of polling page versions
Authentication
An OAuth 2.0 (3LO) app from the Atlassian developer console with granular scopes such as read:page:confluence and write:page:confluence, or basic auth with an Atlassian API token for scripts.

Limits

  • Rate limits are points per hour per app; a global 65,000-point hourly pool is shared across all tenants until a per-tenant pool is granted
  • Webhook delivery is best effort and belongs to the Connect framework, which can no longer be published on the Marketplace; polling is the fallback
  • The v2 attachment endpoints read here list, download, and delete attachments; no upload endpoint appears among them
  • Basic auth with an API token is meant for scripts; a distributable app must use OAuth 2.0 (3LO)

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Confluence ↗

Questions and answers

Does Confluence Cloud send webhooks for page changes?
Yes, through a Connect app descriptor. Events include page_created, page_updated, page_trashed, page_archived, attachment_created, and space_created. Atlassian documents delivery as best effort, and Connect apps can no longer be published on the Marketplace, so this listing also polls page versions.
How are rate limits enforced?
In points per hour, reset at the start of each UTC hour. An app shares a 65,000-point global pool across all tenants until Atlassian grants a per-tenant pool after review. A 429 response carries Retry-After; every response carries X-RateLimit-Remaining and X-RateLimit-NearLimit.
Which content formats does the Page API accept?
A page body can be sent as storage or atlas_doc_format. Reads return the representation you ask for. A page created through POST /pages is published unless you mark it a draft, and each edit through PUT /pages/{id} adds a version.
Ask about Confluence

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Confluence through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy