<aside> 📝

Working draft. Status: research done Oct 26, 2026. Nothing has been built yet.

</aside>

← Back to Projects

Findings

• Roam can create pages and blocks through code with its Backend API (api.roamresearch.com). It uses graph tokens that only the graph's owner can create, doesn't work with encrypted graphs, and is limited to about 100 writes per minute.
• Official roam-tools MCP (needs the Roam desktop app running) and the community 2b3pro/roam-research-mcp, which uses the API.
• No maintained Roam↔Notion sync exists, so the bridge would be something we build, and it would be one-way (Roam → Notion).

Graph links

• Roam's Markdown export + Notion's import keeps [[links]] as plain text.
• roam_2_notion (github.com/melvillian/roam_2_notion, last updated 2024) converts them into Notion mentions.
• Block references, embeds, and Roam queries are lost.

Proposed path

1. One-time import of the Roam export into a "Roam Archive" area in Notion, restoring links with roam_2_notion.
2. A scheduled one-way script into a "Roam Pages" database with a "Links to" relation that keeps the graph of connections.

Open questions

• Which Roam plan the Backend API requires.
• Whether the graph is encrypted.
• Daniel to make a read-only graph token.

Estimated Budget

Estimated Budget: TBD (not yet researched).

Wishlist items