Curiosity

Confluence

Ingests Atlassian Confluence spaces and pages. Two flavours ship in the workspace:

  • Confluence (single-user) — one connector connects with one account; visibility is the union of what that account can see.
  • Confluence (multi-user) — each workspace user connects their own Atlassian account; per-space and per-page access from Confluence is mapped onto access groups.

variant=info text="Knowledge base" variant=success text="OAuth" variant=success text="Maps ACLs"

What gets ingested

Element Mapped to
Space _Space
Page _Page (rendered HTML body, version, labels)
Attachment _FileEntry + _Blob
Page parent/child _HasChild edges, so the page tree is preserved
Authors _Contact

Authentication

  • Type: Atlassian OAuth 2.0 (per-user).
  • The connector refreshes tokens automatically; the refresh token is stored encrypted.
flowchart LR User([User]) -->|click connect| Atlas[Atlassian consent] Atlas --> WS[Workspace] WS -->|access + refresh tokens| Vault[(Secrets)] Vault -->|sign requests| ConfClient[Confluence client] ConfClient -->|API v2| Confluence[(Cloud site)]

Access control mapping

Source Carried into the graph?
Per-user space access Yes (multi-user variant).
Page restrictions (view / edit) Yes — fed through AddPermissionToItem and onto an access group per page.
Anonymous-accessible pages Mapped onto the public access group.

Sync cadence

  • Default cron: every 15 minutes (configurable).
  • Incremental sync: LastUpdated watermark per space; new and updated pages are pulled. Page version is tracked, so re-edits within the same version are skipped.

Notable

  • Ships with a ConfluenceToHtmlConverter for the older "storage format" XML, ensuring rendered HTML stays consistent across page formats.