Sync Memory with Notion

Wato can sync team memory with Notion in both directions:

• Wato → Notion — publish a team's reviewed memory into a Notion workspace.
• Notion → Wato — import a Notion page into a team's memory as a review proposal.

Connect Notion

Sync uses a Notion internal integration:

1. In Notion, create an internal integration and copy its token (starts with secret_).
2. Share the Notion root page you want to use with that integration so it has access.
3. In Wato, go to Settings → Notion sync → Send Wato memory to Notion and enter:
   • Workspace name (optional) — a display label.
   • Root page — the Notion page URL or ID to sync under.
   • Access token — the integration token.
4. Connect.

On connect, Wato creates a per-team database/view under the root page (named {Team} Memory) and runs an initial full sync.

Wato → Notion

Each team's reviewed memory (.md files) is published into its own Notion view. Use the controls on the sync page to refresh:

• Sync recent changes — incremental; only what changed since the last sync.
• Resync everything — full rebuild of the mapped views.

You can enable or disable sync per team. This direction publishes already-reviewed memory, so it doesn't go through review again.

Notion → Wato

Import a single Notion page (and its child pages) into a team's memory under Settings → Notion sync → Import Notion page into Wato:

• Notion page — the page URL or ID.
• Memory path — the target Markdown path, e.g. workflows/notion-import.md.
• Team — which team's memory to import into.

The page is converted to Markdown and submitted as a memory proposal — it does not land directly in reviewed memory. A reviewer approves it in the team's memory review queue before it becomes trusted.

GitHub sync

The same settings area offers Settings → GitHub sync for a one-way Wato → GitHub export: push a team's reviewed memory (and optionally published skills) into a repo at basePath/teamSlug/..., as a full or incremental sync. It's configured the same way (org admin or policies:manage) by pointing at an owner/repo and branch.