Ingest Confluence pages, blog posts, and updates into CortexDB.

Confluence Connector

Captures Confluence space content as CortexDB experiences. Webhooks for real-time; CQL polling as a fallback.

Info

Two ways to run this connector:

  • Run it yourself (Free + paid) — pip install 'cortexdb-connectors[confluence]' then cortexdb-sync sync confluence. The connector reads your token from ~/.cortexdb/state.json (written by cortexdb init) or from env vars.
  • Managed sync (Starter and up) — CortexDB runs the connector as a worker on its infrastructure. Configure it once from your dashboard; CortexDB handles webhook registration, retries, backfill, and idempotency.

1. Prepare credentials in Atlassian

Atlassian → Account Settings → Security → API tokens → Create.

2. Configure in your CortexDB dashboard

  1. Sign in at cortexdb.ai/login.
  2. Settings → Connectors → Add Connector → Confluence.
  3. Paste the Confluence base URL (e.g. https://acme.atlassian.net/wiki), the email of the token owner, and the API token.
  4. Pick the spaces to sync (comma-separated keys, e.g. ENG, RFC).
  5. Set the scope template. Default: org:<your-org>/source:confluence/space:{space_key}.
  6. Pick sync mode: Real-time (webhook) or Polling.
  7. Click Start sync.

What gets written

EventModalityNotes
Page created/updateddocumentTitle + body (HTML → Markdown)
Commentconversationrole=user; preceded_by links to page
Page restored / archivedobservationStatus change as triple

idempotency_key shape: conf:<space>:<page_id>:<version>.

Run it yourself

If you'd rather host the connector yourself instead of using CortexDB's managed worker, every connector ships in the cortexdb-connectors PyPI package:

pip install 'cortexdb-connectors[confluence]'

# Step 1: get a CortexDB token + actor (one-time, free tier)
pip install cortexdb-cli
cortexdb init

# Step 2: supply the connector's third-party credentials
export CONFLUENCE_URL=...                # required
export CONFLUENCE_EMAIL=...                # required
export CONFLUENCE_API_TOKEN=...                # required

# Step 3: one-shot sync, or `watch` for a poll loop
cortexdb-sync sync confluence
cortexdb-sync watch confluence --interval 60

cortexdb-sync reads your CortexDB token + actor from ~/.cortexdb/state.json automatically. Cursor state is persisted in ~/.cortexdb/connectors-state.json, so re-running picks up where the last cycle left off.

See also