Skip to main content
Connect Notion workspaces to automatically sync pages, databases, and content blocks into your Supermemory knowledge base. Supports real-time updates, rich formatting, and database properties.

Quick Setup

1. Create Notion Connection

2. Handle OAuth Flow

After user grants workspace access, Notion redirects to your callback URL. The connection is automatically established.

3. Monitor Sync Progress

Document limit

Each connection has a documentLimit (optional when creating the connection; allowed range 1–10,000). For Notion, each sync run asks the Notion Search API for pages shared with the integration, ordered by last edited time, newest first, and stops after that many pages (or when Search has no more results).
  • Full sync: If your workspace has more shareable pages than documentLimit, the rest are not included in that run. Pages that look “missing” are often older or less recently edited relative to that ordering. Increase documentLimit or trigger another sync after pages change if you need broader coverage.
  • Incremental sync: Only pages edited after the previous sync are candidates; each one still counts toward the same documentLimit. If more pages changed than the limit since last sync, only the first batch in that newest-first order is returned for that run.
Nested and child pages still count as normal pages in Search if the integration can access them—they are not skipped because they are nested. The limit applies to how many pages are fetched per sync, not to depth.

Supported Content Types

Notion Pages

  • Rich text blocks with formatting preserved
  • Nested pages and hierarchical structure
  • Embedded content (images, videos, files)
  • Code blocks with syntax highlighting
  • Callouts and quotes converted to markdown

Notion Databases

  • Database entries synced as individual documents
  • Properties included in metadata
  • Relations between database entries
  • Formulas and rollups calculated values
  • Multi-select and select properties

Block Types

Block TypeProcessingMarkdown Output
TextFormatting preserved**bold**, *italic*, ~~strikethrough~~
HeadingHierarchy maintained# H1, ## H2, ### H3
CodeLanguage detectedpython\ncode here\n
QuoteBlockquote format> quoted text
CalloutCustom formatting> 💡 **Note:** callout text
ListStructure preserved- item 1\n - nested item
TableMarkdown tables`Col 1Col 2\n--------------`
ImageReferenced with metadata![alt text](url)
EmbedLink with context[Embedded Content](url)

Delete Connection

Remove a Notion connection when no longer needed:
Deleting a connection will:
  • Stop all future syncs from Notion
  • Remove the OAuth authorization
  • Keep existing synced documents in Supermemory (they won’t be deleted)

Advanced Configuration

Custom Notion Integration

For production deployments, create your own Notion integration:

Content Filtering

Control which Notion content gets synced:

Workspace Permissions

Notion connector respects workspace permissions:
Permission LevelSync Behavior
AdminFull workspace access
MemberPages with read access
GuestOnly shared pages
No AccessRemoved from index

Database Integration

Database Properties

Notion database properties are mapped to metadata:

Optimization Strategies

  1. Set documentLimit high enough for your workspace size (see Document limit)
  2. Use targeted container tags for efficient organization
  3. Monitor database sync performance for large datasets
  4. Implement content filtering to sync only relevant pages
  5. Handle webhook delays gracefully in your application
Notion-Specific Benefits:
  • Real-time sync via webhooks for instant updates
  • Rich formatting and block structure preserved
  • Database properties become searchable metadata
  • Hierarchical page structure maintained
  • Collaborative workspace support
Important Limitations:
  • Complex block formatting may be simplified in markdown conversion
  • Large databases can take significant time to sync initially
  • Workspace permissions affect which content is accessible
  • Notion API rate limits may affect sync speed for large workspaces
  • Embedded files and images are referenced, not stored directly