Skip to main content
If your team’s documentation already lives in Confluence, you don’t have to start over. The Confluence integration syncs entire spaces into a docs repository, so existing content joins the same Git-backed, agent-maintained workflow as everything else in LivingContext.

​
Connect

1

Authorize with Atlassian

From the Connections page, connect via Atlassian OAuth (3LO). The grant uses granular scopes — only the Confluence permissions the sync needs.
2

Choose a site

The integration supports multiple Atlassian sites. If your account spans several, pick which site the connection targets.
3

Set up a sync job

Open the Sync page (in the Settings sidebar) and use Start a sync: pick a Confluence space and a target docs repository. GitHub must be connected too — the output lands in git.

​
How sync works

Sync is one-way, Confluence → git, run as space → repo jobs:
  • Each job converts one Confluence space’s pages into MDX files with their attachments and opens a pull request on the target repository, so the import itself is reviewable before it merges.
  • Jobs report progress while running, page by page.
  • Completed runs appear in Recent jobs on the Sync page — space, repo, status, page counts, and a link to the PR.
Once synced, the content is ordinary docs in your repository — browsable in the Docs viewer, searchable, editable through change requests, and available as grounding for agents.
Use Confluence sync as a migration path: bring a space across, then let the commit updater and coverage auditor keep it alive — instead of letting it rot in a wiki.

​
Multiple sites and spaces

  • One organization can hold connections to more than one Atlassian site.
  • Each space you want synced gets its own job, so you control exactly what comes across and where it lands.

​
Security

  • Authorization uses Atlassian’s standard OAuth 2.0 (3LO) flow — LivingContext never sees your Atlassian password.
  • Scopes are granular: the connection can read the content it syncs, nothing broader.
  • Tokens are encrypted at rest, like all connection credentials.

​
After the sync

Synced pages behave exactly like any other doc in the repository:

​
Troubleshooting

Confirm the authorizing Atlassian account can access the space, and that you selected the right site when connecting. Reconnect from the Connections page to refresh the grant.
Open the run in the Sync page history for details, then re-run the job. Transient Atlassian API errors usually clear on retry.