Skip to content
Book a demoStart free
Connectors

Confluence connector

Set up the Confluence connector in Kaivo: authentication, configuration, the 5 BigQuery tables it syncs, and answers to common questions.

Confluence connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Confluence data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your project management data instead of moving it.

Sync your Confluence content data into BigQuery with Kaivo to audit pages, spaces, and activity across your workspace.

CategoryProject Management
AuthenticationAPI key
SetupSelf-service

Getting started with the Confluence connector

Section titled “Getting started with the Confluence connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Confluence account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Token.

Field Description
API Token
Your Confluence API token. Generate your token at Manage API tokens.

|

When you set up the connector, you provide:

Field Description
Email
Your Confluence login email

| | Domain name |

Your Confluence domain name

|

Kaivo syncs 5 tables from Confluence into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

audit (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
description STRING A detailed description of the audit event.
category STRING The category under which the audit event falls.
creation_date INT64 The date and time when the audit event was created.
remote_address STRING The IP address from which the audit event originated.
summary STRING A brief summary or title describing the audit event.
super_admin BOOL Indicates if the user triggering the audit event is a super admin.
sys_admin BOOL Indicates if the user triggering the audit event is a system admin.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
blog_posts (16 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
version__created_at TIMESTAMP
version__message STRING
version__number INT64
version__minor_edit BOOL
version__author_id STRING
id STRING
status STRING
title STRING
space_id STRING
author_id STRING
created_at TIMESTAMP
_links__webui STRING
_links__editui STRING
_links__tinyui STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
group (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING The type of group, indicating its category or classification.
id STRING The unique identifier of the group.
name STRING The name of the group.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
pages (21 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
version__created_at TIMESTAMP
version__message STRING
version__number INT64
version__minor_edit BOOL
version__author_id STRING
id STRING
status STRING
title STRING
space_id STRING
parent_id STRING
parent_type STRING
position INT64
author_id STRING
owner_id STRING
last_owner_id STRING
created_at TIMESTAMP
_links__webui STRING
_links__editui STRING
_links__tinyui STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
space (13 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
id STRING
key STRING
name STRING
status STRING
author_id STRING
created_at TIMESTAMP
homepage_id STRING
icon__path STRING
icon__api_download_link STRING
_links__webui STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Confluence supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Confluence?

Section titled “How long does the initial sync take for Confluence?”

It depends on how much history is in your Confluence account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Confluence’s schema changes?

Section titled “What happens when Confluence’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Confluence, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Confluence instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Confluence connector in Kaivo and all of its synced data is deleted with it.

Use pages and space to document how much content lives in each space.

Bring audit into BigQuery to track changes and access over time.

Group pages and blog_posts by space to see where knowledge is concentrated.

Use group to review who has access across your workspace.

Use Confluence data in your AI and BI tools

Section titled “Use Confluence data in your AI and BI tools”

Once Confluence data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Confluence data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Confluence connector pricing and plan details.

  • ClickUp: Sync ClickUp to BigQuery.
  • GitHub: Sync GitHub to BigQuery.
  • GitLab: Sync GitLab to BigQuery.
  • Harvest: Sync Harvest to BigQuery.
  • Jira: Sync Jira to BigQuery.
  • Kellokortti: Sync Kellokortti to BigQuery.