> 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/finance-and-accounting/concord/faq.md).

# FAQ

<details>

<summary>Can I connect multiple Concord organizations to Coupler.io?</summary>

Yes. Each Concord organization has its own API key. Create a separate data flow for each organization, then use Coupler.io's **Append** transformation to combine the data into one unified dataset. It's a good idea to add a column in each flow to label the source organization so you can tell records apart downstream.

</details>

<details>

<summary>Which Concord entities are available in Coupler.io?</summary>

Coupler.io supports seven Concord entities: Agreements, Organizations, Organization members, User organizations, Folders, Reports, and Tags. Agreements is the most data-rich entity and the best starting point for most use cases.

</details>

<details>

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

Log into Concord and go to **Settings > API**. If you don't see an API section, your account plan may not include API access — check with your Concord administrator or contact Concord support to confirm your plan includes it.

</details>

<details>

<summary>Does Coupler.io support incremental sync for Concord?</summary>

Coupler.io's Concord connector is built on Airbyte. Whether incremental sync is supported depends on the stream — Agreements typically supports incremental updates based on modification timestamps, while some smaller reference entities like Tags may perform a full refresh each time. Check the sync results in your data flow run history to see which mode each entity uses.

</details>

<details>

<summary>Can I use Concord data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route Agreements or Reports data directly to these tools — for example, to generate contract summaries, flag unusual terms, or answer questions about your contract portfolio.

</details>

<details>

<summary>Why do tag names show up as IDs in my Agreements data?</summary>

The Agreements entity stores tag and folder references as IDs, not names. To get human-readable labels, add the Tags and Folders entities as additional sources in your data flow and use Coupler.io's **Join** transformation to match IDs to names. See the Data Overview article for suggested field combinations.

</details>

<details>

<summary>How do I track contracts that are expiring soon?</summary>

Pull the Agreements entity and use the expiration date field in your destination tool to filter or sort by upcoming dates. In Google Sheets or Looker Studio, you can create a calculated column that flags agreements expiring within a set number of days. For automated alerts, route the data to a tool like Google Sheets and set up conditional notifications there.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](/sources/category/finance-and-accounting/concord/data-overview.md) article. If you're running into sync errors or missing records, check [Common Issues](/sources/category/finance-and-accounting/concord/common-issues.md) for fixes.
{% 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/finance-and-accounting/concord/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.