Source connector

Confluence connector

Confluence integration for databases, warehouses and BI tools

Team wiki and documentation workspace. Datrise captures Confluence entities such as spaces, pages, blog posts, comments, attachments and page versions, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Confluence Cloud REST API v2 authenticates with OAuth 2.0, HTTP Basic, API key, incremental runs key on version.createdAt, and Confluence caps calls at Points-based hourly quota: Free/Standard tenants share a 65,000-point/hour pool, Standard/Premium/Enterprise get per-tenant pools (e.g. Enterprise 150,000 base + 30 points per user/hour) capped at 500,000 points/hour, with most read calls costing 1 point.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `confluence_spaces`) with a schema derived from the Confluence API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Confluence pipeline page, and join the waitlist to get the Confluence connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Confluence data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
spaces	confluence_spaces	Upsert by primary key, incremental on updated-at
pages	confluence_pages	Upsert by primary key, incremental on updated-at
blog posts	confluence_blog_posts	Upsert by primary key, incremental on updated-at
comments	confluence_comments	Upsert by primary key, incremental on updated-at
attachments	confluence_attachments	Upsert by primary key, incremental on updated-at
page versions	confluence_page_versions	Upsert by primary key, incremental on updated-at

Confluence API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Confluence Cloud REST API v2
Authentication	OAuth 2.0, HTTP Basic, API key — OAuth 2.0 (3LO) via an Atlassian app is preferred for user-context access; direct scripts commonly use HTTP Basic auth with an Atlassian account email plus an API token instead of a password.
Pagination	cursor — List endpoints (e.g. GET /wiki/api/v2/pages) take `limit`/`cursor` query params; the opaque next-page cursor is returned in the response's `Link` header and in `_links.next`.
Rate limit	Points-based hourly quota: Free/Standard tenants share a 65,000-point/hour pool, Standard/Premium/Enterprise get per-tenant pools (e.g. Enterprise 150,000 base + 30 points per user/hour) capped at 500,000 points/hour, with most read calls costing 1 point.
Incremental cursor	version.createdAt — Every page/blogpost carries a `version` object with `version.createdAt` and a monotonically increasing `version.number`, but v2 list endpoints do not publish a documented `modified-since` query filter, so incremental extraction typically means paging the full `cursor` list and diffing `version.number` client-side.
Webhooks	Yes — Confluence Cloud webhooks (event-based, e.g. page_created / page_updated / page_removed)
Bulk export	No
Deletes detectable	Yes — The `status` query parameter on list endpoints accepts `trashed` (soft-deleted pages sit in the space trash before permanent purge), giving a filterable deleted-record signal.

Official API reference

What bites when replicating Confluence

REST API v2 enum values (e.g. `status`) are documented in lower_case but some endpoints have returned UPPER_CASE values in practice, so parsers should normalise case rather than doing exact string matches.
The `status` field can be `current`, `archived`, `trashed`, `historical`, or `draft`, but v2's update endpoint can only set a page to `current`, `trashed`, `historical`, or `draft` — archiving still requires the older v1 endpoint.
Rate-limit responses return HTTP 429 with `Retry-After`, `X-RateLimit-Limit`, and `X-RateLimit-Reset` headers, and the points quota resets on the UTC hour with no carry-over, so bursts near the top of the hour can starve the next window.
OAuth 2.0 (3LO) refresh tokens rotate on every use and expire after 90 days of inactivity, so a connector that only syncs quarterly can silently lose its refresh token and need full re-authorization.

Compare this against every other documented API

Popular destinations for Confluence

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Confluence connector FAQ

What Confluence data does the connector extract?: 6 objects: spaces, pages, blog posts, comments, attachments and page versions. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Confluence integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Confluence data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Confluence → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Confluence pipeline with guided onboarding

Join the waitlist to get priority access for Confluence integrations with guided setup, schema-aware mapping, and production-grade incremental sync.