Superhuman Docs (Coda)
Keep Superhuman Docs and tables in sync with your agents
How the Superhuman Docs (Coda) source works
Superhuman Docs, formerly Coda, mixes prose with structured tables, which makes it a natural retrieval source for agents: the runbook and the escalation matrix live in the same place. The source syncs both into your Connic retrieval.
You 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 schedule you choose.
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
Everything you control when 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
- Category
- Retrieval Sources
- Type
- Docs
- Sync schedule
- Every 15 minutes to weekly
- Documentation
- Retrieval Docs
Superhuman Docs (Coda) retrieval source FAQ
Tell us where your content lives, how fresh it needs to be, and who is allowed to see it. We will map that to source scopes, namespaces, and the retrieval setup your agents need.
Talk to Sales