Skip to main content
The Coda connector indexes the pages and the tables of every Coda doc that the configured API token can open. There is no doc picker. Onyx indexes every doc the token’s Coda account can reach.

​
How it works

Each refresh re-reads the docs the token can open and indexes the pages and tables changed since the last run. A table whose rows cannot be read is still indexed from its name alone, so the table appears in search even when its contents are unavailable.
The connector indexes everything the token’s account can open, and the access type applies to all of it at once. A token belonging to a user with wide Coda access, combined with Everyone in Your Organization, makes every doc that user can read visible to every Onyx user. Create the token from an account whose Coda access matches what you want in Onyx.

​
Before you begin

You need:
  • A Coda account that can open the docs you want Onyx to index
  • A Coda API token for that account
  • An Onyx administrator account

​
Configure Coda

1

Generate an API token

In Coda, open your account settings and generate an API token. Copy it right away.See Coda’s API authentication documentation for their current steps.

​
Configure Onyx

1

Connect a Coda account

In Onyx, go to Admin Panel → Connectors and select Coda. Under Authentication Account, select New Coda Account and paste the token into API Token. Onyx checks the token when you create the connector and rejects it if Coda returns an authentication error.Create a Coda account with a display name and the Coda API token
2

Name the connector

Coda has no other connector settings: the token decides what is indexed.
3

Choose who can see the content

Under Document Access, select Everyone in Your Organization or Specific Groups. Specific Groups is available on Onyx Cloud and Enterprise Edition.
4

Create and verify

Select Create Connector. Then open Admin Panel → Indexing Status, select the connector, and confirm its first indexing attempt completes.

​
Limits

Onyx rate-limits its own calls to the Coda API. The connector downloads no files, so it has no file-size cap: it indexes page text and table cell values through the API.

​
Troubleshooting

Coda credential appears to be invalid or expired (HTTP 401) means the token is wrong or has been revoked. Generate a new token in Coda and update the Onyx credential.
Coda workspace not found or not accessible (HTTP 404) means the token’s account cannot reach the workspace. Confirm the workspace is shared with that account.
Validation failed due to Coda rate-limits being exceeded (HTTP 429) means Coda is throttling the account. Wait and retry. Onyx already rate-limits and retries its own calls, so a persistent 429 usually means something else is also using the token.
Confirm the token’s Coda account can open it. Onyx indexes only what that account can reach, so a doc shared with a different account is not indexed. A table whose rows cannot be read is indexed from its name alone.