Skip to main content
Connic

Retrieval Sources

Connect the places where teams already write: Notion, Confluence, Superhuman Docs (Coda), or any website. Connic syncs their content into agent retrieval on a schedule, so answers stay current without manual uploads.

Retrieval DocsQuickstart

Featured

Notion

By Connic

Connect a Notion workspace and keep pages and databases synced in retrieval. Agents retrieve the current version, not a stale export.

Workspace appAuto-sync
View details

Website Crawler

By Connic

Point the crawler at documentation, a help center, or a blog. Pages are converted to clean markdown and re-crawled on the configured schedule.

WebsiteAuto-sync
View details

All retrieval sources

4 matching entries

Notion

By Connic

Connect a Notion workspace and keep pages and databases synced in retrieval. Agents retrieve the current version, not a stale export.

Workspace appAuto-sync
View details

Confluence

By Connic

Sync Confluence spaces on a configured schedule. Pages are chunked and embedded so agents can answer from the wiki instead of guessing.

WikiAuto-sync
View details

Superhuman Docs (Coda)

By Connic

Sync Superhuman Docs pages and table rows into retrieval, so agents answer from the doc the team actually edits.

DocsAuto-sync
View details

Website Crawler

By Connic

Point the crawler at documentation, a help center, or a blog. Pages are converted to clean markdown and re-crawled on the configured schedule.

WebsiteAuto-sync
View details

How retrieval sources work

One pipeline for every source: connect, scope, sync, retrieve.

  1. Connect a source

    Authorize Notion, Confluence, or Superhuman Docs (Coda) with a scoped token, or point the website crawler at a URL. Connected sources read only explicitly shared content; the crawler stays inside its configured boundaries.

  2. Scope what syncs

    Select spaces, pages, databases, labels, or crawl boundaries. Content outside the scope is never read, and every source syncs into a selected namespace.

  3. Sync on a schedule

    From every 15 minutes for API-backed sources, or every 12 hours for website crawls, up to weekly, Connic pulls changed content, converts it to clean text, chunks it, and embeds it for semantic search. Unchanged pages are skipped.

  4. Agents retrieve it

    Every agent in the project can query the retrieval at run time and answer from the freshest synced version, with namespaces to keep sources separated.

Retrieval sources FAQ

Retrieval sources automatically sync external content into a project's Retrieval. A single connection to Notion, Confluence, Superhuman Docs (Coda), or a website keeps content chunked, embedded, and retrievable on the configured schedule without manual uploads.

Uploads are one-time snapshots; a synced source stays current. When someone edits the wiki page or publishes a new doc, the next sync updates the retrieval without anyone re-uploading anything. Both end up in the same retrieval and are retrieved the same way.

Notion, Confluence, and Superhuman Docs (Coda) for internal content, plus a website crawler for anything public like docs or help centers. More sources are on the way.

Each page is converted to clean text, split into chunks, and embedded for semantic search in the project's Retrieval under a namespace for each source. Agents query it at run time and retrieve the most relevant chunks regardless of their source.

No. Retrieval sources are read-only by design: content is pulled into retrieval, never written back. When an agent should act on an external system, that is what connectors are for.