Skip to main content
Connic

Superhuman Docs (Coda)

By Connic

Keep Superhuman Docs and tables in sync for agents

DocsAuto-sync

How the Superhuman Docs (Coda) source works

Superhuman Docs, formerly Coda, keeps prose and structured tables together. The source syncs both the runbook and the escalation matrix into Connic retrieval.

Connect with a Superhuman Docs API token and pick the docs to sync. Pages are converted to text, and table rows become individual entries with their column values preserved, so an agent can retrieve one row as precisely as one paragraph. Everything refreshes on the configured schedule.

What gets synced

Pages

Doc pages and subpages, converted to clean text before chunking.

Tables

Each row becomes its own retrieval entry with column values preserved.

Doc structure

Page hierarchy is kept in entry metadata so retrieval can be scoped later.

Configuration, in depth

Every available control for connecting Superhuman Docs (Coda) to a project.

Connection

API token*
Superhuman Docs API token. The sync only reads docs this token can access.

Content scope

Docs
Superhuman Docs links or IDs, one per line. Existing coda.io links also work. Leave empty to sync every doc the token can read.
Include hidden pages
Also sync pages that are hidden in the doc's navigation.
Include tables
Sync table rows as individual retrieval entries.

Sync behavior

Where synced content lands and how often it refreshes.

Target namespace
Retrieval namespace the synced entries are filed under. Use dots to nest, e.g. sources.notion.
Sync interval
How often the source is checked for changes. Each run only reprocesses content that changed.
When content is deleted at the source
Pages or rows deleted in Superhuman Docs can be removed from the retrieval on the next sync, or kept as they were last synced.

Information

Publisher
By Connic
Type
Docs
Sync schedule
Every 15 minutes to weekly
Documentation
Retrieval Docs

Superhuman Docs (Coda) retrieval source FAQ

It syncs the pages and tables of the selected docs. Pages are converted to text, and each table row becomes its own retrieval entry with column values preserved.

Yes. Rows are stored as separate entries, so a semantic query like an escalation contact or a pricing rule can surface exactly the matching row.

List specific doc links or IDs in the configuration. If the list is empty, every doc the API token can read is kept in sync.

Yes. Superhuman Docs continues to accept existing Coda API tokens and coda.io links, so current connections do not need to be recreated.
Need Superhuman Docs (Coda) content behind a production agent?

Our team maps content location, freshness requirements, and access rules to source scopes, namespaces, and the required agent Retrieval setup.

Talk to Sales