Supported Connectors
Google Drive
Google Docs, Slides, SheetsReal-time sync via webhooks. Supports shared drives, nested folders, and collaborative documents.
Gmail
Email ThreadsReal-time sync via Pub/Sub webhooks. Syncs threads with full conversation history and metadata.
Notion
Pages, Databases, BlocksInstant sync of workspace content. Handles rich formatting, embeds, and database properties.
OneDrive
Word, Excel, PowerPointScheduled sync every 4 hours. Supports personal and business accounts with file versioning.
GitHub
GitHub RepositoriesReal-time incremental sync via webhooks. Supports documentation files in repositories.
Granola
Meeting notes and transcriptsSyncs AI meeting notes, summaries, attendees, and transcripts from your Granola workspace.
Web Crawler
Web Pages, DocumentationCrawl websites automatically with robots.txt compliance. Scheduled recrawling keeps content up to date.
Quick Start
1. Create Connection
2. Handle OAuth Callback
After user completes OAuth, the connection is automatically established and sync begins.3. Monitor Sync Status
How Connectors Work
Authentication Flow
- Create Connection: Call
/v3/connections/{provider}to get an OAuth URL, or create a direct credential-based connection for Granola or Web Crawler - User Authorization: Redirect user to complete OAuth flow when the provider requires it
- Automatic Setup: Connection established, sync begins immediately
- Continuous Sync: Real-time updates via webhooks + scheduled sync every 4 hours (or scheduled recrawling for Web Crawler)
Document Processing Pipeline
Sync Mechanisms
Connection Management
List All Connections
Delete Connections
TheDELETE /v3/connections/:connectionId endpoint accepts an optional deleteDocuments query parameter:
Setting
deleteDocuments=false is useful when you want to disconnect an integration without losing the memories that were already imported.Custom OAuth Applications
By default, Supermemory uses its own OAuth applications to connect to third-party providers. You can configure your own OAuth app credentials viaPATCH /v3/settings for tighter control over data access — useful for enterprise customers.
- Create the OAuth application on the provider’s developer console:
- For Google Drive specifically: choose application type Web application, and enable the Google Drive API under “APIs and Services” in the Cloud Console. Google also requires verification/approval before custom keys work in production.
- Set the redirect URL to
https://api.supermemory.ai/v3/connections/auth/callback/{provider}(for example,.../auth/callback/google-drive).