Connector library

Implemented source Collaboration & Productivity APIs

Confluence connector.

Read Confluence Cloud pages and their storage-format bodies, list space pages, create draft/published pages and update published pages with an explicit next version through REST API v2.

Connector download

Download Confluence

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
9 KB
SHA-256
378ab971a8cd91c07a90029806fa10c1301a696cd0a86373e1383aa8bfd7a64e

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Read Confluence Cloud pages and their storage-format bodies, list space pages, create draft/published pages and update published pages with an explicit next version through REST API v2.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get page and version

Retrieve the storage body and version; getDraft optionally selects a draft.

List space pages

Retrieve one bounded page of published pages in a space.

Create page

Create a draft by default, or explicitly publish with status=current.

Update published page

Replace a current page body/title using the version from the latest retrieval.

Vendor API

API and access

Implementation considerations
  • Confirm project IDs, board/list IDs, status transition rules, custom fields, and user mapping before enabling writes.
  • Use external IDs or links back to source records so duplicate workflow retries do not create duplicate tasks.
  • For broad work-management APIs, start with create/update/comment/transition before advanced reporting.

Support

Need help with Confluence?

Tell us what you need to connect or change.