Integrations / Coda
Coda
Coda docs and tables for product specs, operating cadences, planning trackers, and lightweight internal apps.
Bearer token
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A Coda account that can open the docs Telara should see.
The user whose docs you want indexed — tokens are per-user.
Vendor setup
Get the credential
1
Open account settings
In Coda, click your avatar → Account settings → API settings (Generate API token).
2
Generate a token
Click Generate API token. Copy it immediately. Coda will not show it again.
3
Paste in Telara
Settings → Integrations → Coda. Paste the token into the field Telara shows.
In Telara
Connect in Telara
Bearer token
Coda API token generated from the user profile settings.
In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.
Fields Telara asks for
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Doc | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Doc | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Doc.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Docs the token’s user cannot open stay out of Telara, including docs shared only with a different teammate.
Pack-only tokens are the wrong class if Telara asks for a personal API token.