FAQ

Where do I find my Coda API key?

Go to coda.io/account and scroll to API settings. Click Generate API token, give it a name, and copy the token. Paste it into the API key field when setting up your Coda data flow in Coupler.io.

How do I find the doc ID and table ID I need for the Rows entity?

Open the Coda doc in your browser. The doc ID is the alphanumeric string after /d/ in the URL. The table ID appears after the # symbol. You can also run a Tables data flow first — it returns all table IDs and names for a given doc, making it easy to find the right one.

Can I pull data from multiple Coda docs in one data flow?

Yes. You can add multiple sources to a single data flow in Coupler.io — each pointing to a different doc or table. Use the Append transformation to stack the results into one dataset, or Join to combine them on a shared key.

Why do my column names look like IDs instead of the names I set in Coda?

Coda's API returns column identifiers in some cases rather than display names. This is a known behavior of the Coda API. You can rename columns in Coupler.io using column mapping, or rename them directly in your destination after the first sync.

Can I send Coda data to an AI tool like ChatGPT or Claude?

Yes. When setting up your data flow, select an AI destination instead of a spreadsheet or database. Coupler.io supports ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This is useful for summarizing Coda table data, generating reports, or asking questions about your structured data.

Does Coupler.io support Coda views, or only base tables?

The Rows entity pulls from the table or view you specify by ID. This means you can target a filtered or sorted view if you want a subset of rows. Keep in mind that hidden columns in a view may not be returned — use the base table ID if you need all columns.

What happens if my Coda API key is rotated or deleted?

All data flows using that key will fail immediately. To fix this, generate a new API key in Coda and update the connection in Coupler.io. To avoid widespread disruption, use a dedicated API key for Coupler.io so rotating it only affects this integration.

For details on what fields are available for each entity, see Data Overview. For help with sync errors, visit Common Issues. For setup recommendations, check Best Practices.