Common Issues

Connection issues

Invalid API key error when connecting

Double-check that you copied the full API key from Coda Account settings → API settings. API keys in Coda start with 4a6f... and are long strings — partial copies are a common cause of auth failures. Also confirm that the key hasn't been revoked or regenerated since you last used it.

Connection succeeds but no data appears

This usually means the API key belongs to a Coda account that doesn't own or have access to the docs you're trying to pull. Make sure the API key is from the account that has read access to the relevant docs and tables.

Missing data

Rows entity returns no results

The Rows entity requires a specific doc ID and table ID. If either is missing or incorrect, the sync will return empty. Verify both IDs in the Coda URL — the doc ID appears after /d/ and the table ID after # in the browser address bar.

Some columns are missing from the Rows export

Coda returns row values as nested key-value pairs using column IDs, not display names. If certain columns aren't appearing, check whether those columns exist in the specific table view you're syncing — hidden columns in a view may not be returned by the API.

Sync tables show up in Tables entity but have no rows

Sync tables in Coda pull data from external sources and may not always be fully populated. If the external sync hasn't run recently in Coda, the rows won't be available via the API either. Trigger a sync refresh in Coda first, then re-run your Coupler.io data flow.

Permission errors

403 Forbidden when accessing a specific doc

The API key you're using belongs to a user who doesn't have access to that doc. In Coda, access is per-doc — being an admin on one doc doesn't grant access to others. Ask the doc owner to share it with your account, then re-run the data flow.

Data discrepancies

Row counts in Coupler.io don't match what I see in Coda

Coda may return paginated results and very large tables can be truncated if API rate limits are hit during a sync. Check whether filtered views are being used — the Rows entity respects the default view, which may exclude some rows. Try syncing from the source table rather than a filtered view.

Rate limits

Sync fails or times out on large tables

Coda's API has rate limits that can slow down or interrupt syncs for tables with thousands of rows. If you're hitting this consistently, try splitting large tables into multiple data flows or scheduling syncs during off-peak hours to reduce the chance of collisions with other API activity.