Adopt

5 surfaces

Surfaces

Integrations

Strategy & Discovery

2
VistalyProductboard

Research & Insights

1
Dovetail

Knowledge & Docs

1
Notion

Design

1
Figma

Analytics

1
PostHog
Knowledge & DocsBeta

Coming from Confluence

18% entity overlap

Import

Confluence pages become typed document nodes: ADRs, specs, and research classified by label.

The structural finding

Confluence is where product knowledge goes to become untracked. The adapter rescues it: pages labelled "adr" become decision nodes, "research" becomes research_study, "persona" becomes persona. Everything else becomes document, which is the beginning of a typed knowledge graph.

What UPG adds

1

Type recovery: untyped Confluence pages classified by label into ADRs, research studies, personas, and specs.

2

Graph edges: Confluence pages linked to the features, opportunities, and decisions they describe.

3

Jira bridge: Confluence ADRs connected to the Jira epics they influenced, closing the decision traceability loop.

Schema mapping

Direct matches
Page (generic)→document
Blog Post→content_piece
Template→documentation_template
Space→product_areaA Space is a product area boundary, partial match
Maps with caveats
Page (labelled "adr")→decisionLabel-based discrimination
Page (labelled "research")→research_study
Page (labelled "persona")→persona
Page (labelled "prd")→documentWith feature extraction via AI assist
Whiteboard→wireframeVisual canvas, rough match
What UPG adds
opportunityhypothesisexperimentmetricfeature (without extraction)
Skipped:Comments · Smart Links · Checkbox tasks · Space permissions

The key edge

The single most important semantic relationship this integration enables.

node_informs_node

Defined in the UPG specification

Sample import

Confluence space: pages classified by label → typed UPG nodes

Input (from Confluence)
Output (UPG nodes)
Page (label: adr)
ADR-001: Use Postgres for graph storage
→
decision
ADR-001: Use Postgres for graph storage
↳ document_describes_decision
Page (label: research)
User research report Q2 2026
→
research_study
User research report Q2 2026
Page (label: persona)
The Ambitious PM persona
→
persona
The Ambitious PM persona
Blog Post
Product Update: May 2026
→
content_piece
Product Update: May 2026

How to import your Confluence data

Via the CLI (coming soon)

The Confluence adapter is built and tested. A one-command import via the UPG CLI is in development:

npx unified-product-graph import --from confluence

This will fetch your Confluence data, map entity types automatically, and write everything to your graph. Today you can use the Markdown import or the adapter directly in code.

▸ For developers: use the adapter directly
import { ConfluenceAdapter } from '@unified-product-graph/adapters'
// Pass pre-fetched Confluence data as SourceItem[]
const adapter = new ConfluenceAdapter()
const result = await adapter.convert(items)
// result.nodes → typed UPG entities
// result.edges → canonical relationships
// result.warnings → items needing review

Get started

The Confluence adapter ships in @unified-product-graph/adapters. Install it, then run the import command.

# one-time install
$ npm install -g unified-product-graph

# then import
$ upg import --from notion

Other tools in Knowledge & Docs

← All integrations