MemorySync
Integrations

Connectors Overview

Connectors bring supported content from an external source — developer platforms, team wikis, document storage, team chat, or permitted public websites — into MemorySync, so your application retrieves it alongside its own memories. Each connector below documents its source boundary and update model.

Find the right source

Choose the kind of knowledge you want to retrieve. The finder recommends one external source and links to its real guide.

What knowledge do you want to bring in?

Best for · Engineering context

GitHub

Repository, issue, pull-request, review, and discussion context from repositories you grant access to.

RepositoriesIssuesPull requests
Explore GitHub

This finder only recommends and navigates to an external source guide. It does not connect an account or change your project.

External source connectors

External source
GitHub

Repository and collaboration context for engineering teams.

RepositoriesIssuesPull requests
Incremental ingestion
Explore GitHub
External source
Notion

Shared workspace pages, blocks, and nested knowledge.

Shared pagesBlocksNested content
Resynchronization
Explore Notion
External source
Google Drive

Supported documents, PDFs, and file metadata.

DocumentsPDFsMetadata
Synchronization
Explore Google Drive
External source
OneDrive

Permitted Office files and SharePoint libraries.

Office filesOneDriveSharePoint
Per-drive incremental deltas
Explore OneDrive
External source
Slack

Messages and threads from approved channels.

MessagesThreadsApproved channels
Per-channel updates with event-driven changes
Explore Slack
External source
Granola

AI meeting notes and transcripts from approved folders.

Meeting notesTranscriptsApproved folders
Per-folder updates with event-driven changes
Explore Granola
External source
Amazon S3

Documents from approved bucket paths in object storage.

DocumentsApproved pathsS3-compatible
Scheduled sync with change detection by ETag
Explore Amazon S3
External source
Web Crawler

Permitted public pages from a single website.

Public pagesSame originPlain text
One-time background job
Explore Web Crawler

From source to retrieval

  1. 1
    Connect

    Authorize a supported source or provide a permitted public starting page.

  2. 2
    Select or share

    Keep the source boundary limited to the knowledge you intend to import.

  3. 3
    Import

    MemorySync extracts supported content through the connector’s update model.

  4. 4
    Retrieve

    Query imported knowledge alongside other memories in the project.

Compare connectors

SourceRepresentative contentUpdate style
GitHubRepositories, issues, pull requests, and recent commitsIncremental ingestion
NotionExplicitly shared pages, blocks, and supported nested contentResynchronization
Google DriveSupported files and metadata, including documents and PDFsSynchronization
OneDriveDOCX, PPTX, XLSX, text, OneDrive, and SharePoint librariesPer-drive incremental deltas
SlackMessages, thread replies, and text from files shared in approved channelsPer-channel updates with event-driven changes
GranolaAI summaries and full transcripts for meetings in approved foldersPer-folder updates with event-driven changes
Amazon S3Readable documents under approved bucket pathsScheduled sync with change detection by ETag
Web CrawlerPermitted same-origin public pages with extractable plain textOne-time background job

Permissions and next steps

Keep the source boundary narrow
A connector only works within its documented source boundary. Grant or share only the content needed for the retrieval use case, and review who can use the imported knowledge.

After a small verification import, use the Query API, the Python SDK, or the Node.js SDK to retrieve content from your application.

Was this page helpful?
← Previous
AWS Bedrock
Next →
GitHub