# Linking Confluence as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Confluence connector pulls your Atlassian Confluence Cloud content — spaces, pages, blog posts, attachments, and more — into the PostHog data warehouse. Only Confluence Cloud sites (`your-domain.atlassian.net`) are supported.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Confluence.
3.  You need your Confluence Cloud subdomain, account email, and an API token. Create an API token from your [Atlassian account settings](https://id.atlassian.com/manage-profile/security/api-tokens). Your **Subdomain** is the `your-domain` part of `your-domain.atlassian.net`. Use the **Email** address tied to the Atlassian account that owns the token.
4.  Back in PostHog, enter the `Subdomain`, `Email`, and `API token`, then click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Confluence data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| spaces | Confluence spaces | Full refresh |
| pages | Pages across your site | Full refresh |
| blogposts | Blog posts | Full refresh |
| attachments | Attachments | Full refresh |
| tasks | Tasks | Full refresh |
| labels | Labels | Full refresh |
| footer_comments | Footer comments | Full refresh |
| inline_comments | Inline comments | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

All Confluence tables are full refresh only. The Confluence Cloud v2 list endpoints do not expose a server-side timestamp filter, so each sync reloads the full collection.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Subdomain | text | Yes |
| Email | email | Yes |
| API token | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| spaces | A Confluence space — a top-level container that groups related pages and content. | Full refresh | — | — |
| pages | A Confluence page — a unit of content that lives within a space. | Full refresh | — | — |
| blogposts | A Confluence blog post — a dated post that lives within a space. | Full refresh | — | — |
| attachments | A file attachment associated with a page, blog post, or other Confluence content. | Full refresh | — | — |
| tasks | An action item (checkbox task) embedded within Confluence content. | Full refresh | — | — |
| labels | A label (tag) that can be applied to Confluence content for categorization. | Full refresh | — | — |
| footer_comments | A footer comment left at the bottom of a Confluence page or blog post. | Full refresh | — | — |
| inline_comments | An inline comment anchored to specific text within a Confluence page or blog post. | Full refresh | — | — |

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better