> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/files-and-tables/coda/faq.md).

# FAQ

<details>

<summary>Where do I find my Coda API key?</summary>

Go to [coda.io/account](https://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.

</details>

<details>

<summary>How do I find the doc ID and table ID I need for the Rows entity?</summary>

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.

</details>

<details>

<summary>Can I pull data from multiple Coda docs in one data flow?</summary>

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.

</details>

<details>

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

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.

</details>

<details>

<summary>Can I send Coda data to an AI tool like ChatGPT or Claude?</summary>

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.

</details>

<details>

<summary>Does Coupler.io support Coda views, or only base tables?</summary>

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.

</details>

<details>

<summary>What happens if my Coda API key is rotated or deleted?</summary>

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.

</details>

{% hint style="info" %}
For details on what fields are available for each entity, see [Data Overview](/sources/category/files-and-tables/coda/data-overview.md). For help with sync errors, visit [Common Issues](/sources/category/files-and-tables/coda/common-issues.md). For setup recommendations, check [Best Practices](/sources/category/files-and-tables/coda/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/files-and-tables/coda/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.