> 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.md).
# Concord
Connect Concord contract data — agreements, members, folders, and reports — to Google Sheets, BigQuery, or AI tools via Coupler.io.
Concord is a contract lifecycle management (CLM) platform that helps teams create, negotiate, sign, and manage agreements in one place. It centralizes contract data across organizations, making it easier to track obligations, deadlines, and counterparties.
Connecting Concord to Coupler.io lets you pull contract data into your reporting and analytics tools without manual exports. Here's why teams do it:
* **Track agreement status** across your entire contract portfolio in Google Sheets, Excel, or Looker Studio
* **Combine contract data with financial records** using Join or Append transformations
* **Feed contract insights into AI tools** like ChatGPT, Claude, or Gemini for summaries and risk analysis
* **Automate reporting** so stakeholders always have up-to-date data without chasing exports
## Prerequisites
Before connecting, make sure you have:
* An active Concord account with API access enabled
* A Concord API key (available in your account settings)
* Sufficient permissions to read the entities you want to sync (agreements, members, reports, etc.)
## Quick start
{% hint style="success" %}
Start with the **Agreements** entity — it's the core of Concord and gives you the most actionable data right away.
{% endhint %}
## How to connect
{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Go to your Coupler.io dashboard and click **Add data flow**. Search for and select **Concord** as your source.
{% endstep %}
{% step %}
**Enter your Concord API key.** In the source settings, paste your Concord API key into the authentication field. You can find this key in your Concord account under Settings > API.
{% endstep %}
{% step %}
**Select an entity.** Choose the entity you want to import — for example, Agreements, Organization members, or Reports.
{% endstep %}
{% step %}
**Choose a destination.** Pick where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}
{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Concord data will appear in your chosen destination.
{% endstep %}
{% endstepper %}
## Concord data overview
Coupler.io pulls data from seven Concord entities. This page breaks down what fields are available in each and how you can use them together.
## Entities overview
| Entity | Best used for |
| -------------------- | ------------------------------------------------------------------- |
| Agreements | Contract status tracking, renewal monitoring, obligation management |
| Organizations | Org-level settings and configuration |
| Organization members | User access audits, team structure |
| User organizations | Mapping users to their org roles |
| Folders | Understanding how contracts are structured and categorized |
| Reports | Pre-built analytics and contract insights from Concord |
| Tags | Contract categorization and filtering |
## Agreements
#### Key fields
| Field | Description |
| --------------- | ----------------------------------------------------- |
| Agreement ID | Unique identifier for each contract |
| Title | Name or subject of the agreement |
| Status | Current state (e.g., draft, pending, active, expired) |
| Type | Category of agreement (e.g., NDA, MSA, SOW) |
| Created date | When the agreement was created |
| Effective date | When the contract becomes active |
| Expiration date | When the contract expires |
| Owner | User responsible for the agreement |
| Counterparty | External party to the contract |
| Tags | Labels applied to the agreement |
| Folder | Folder the agreement is stored in |
## Organizations
#### Key fields
| Field | Description |
| --------------- | ----------------------------- |
| Organization ID | Unique identifier for the org |
| Name | Organization name |
| Plan | Subscription plan or tier |
| Created date | When the org was created |
## Organization members
#### Key fields
| Field | Description |
| ----------- | ------------------------------------- |
| Member ID | Unique identifier for the member |
| User ID | Associated user account |
| Role | Member's role within the organization |
| Status | Active or inactive membership |
| Joined date | When the user joined the org |
## User organizations
#### Key fields
| Field | Description |
| --------------- | ----------------------------------------- |
| User ID | Identifier of the user |
| Organization ID | Identifier of the associated organization |
| Role | User's role in that organization |
## Folders
#### Key fields
| Field | Description |
| ---------------- | ----------------------------------------------- |
| Folder ID | Unique identifier for the folder |
| Name | Folder name |
| Parent folder ID | ID of the parent folder (for nested structures) |
| Created date | When the folder was created |
## Tags
#### Key fields
| Field | Description |
| ------ | -------------------------------- |
| Tag ID | Unique identifier for the tag |
| Name | Tag label |
| Color | Visual color assigned to the tag |
## Reports
#### Key fields
| Field | Description |
| ------------ | ----------------------------- |
| Report ID | Unique identifier |
| Name | Report title |
| Type | Category of report |
| Created date | When the report was generated |
| Data | Report content and metrics |
## Common field combinations
* **Agreements + Tags** — Join on tag ID to filter and group contracts by category (e.g., vendor, customer, legal)
* **Agreements + Folders** — Join on folder ID to understand how contracts are distributed across your folder hierarchy
* **Organization members + User organizations** — Join on user ID to build a full picture of who has access to what across multiple orgs
* **Agreements + Reports** — Combine raw agreement data with Concord's pre-built report summaries for richer dashboards
## Use cases by role
{% tabs %}
{% tab title="Legal & Contracts" %}
* Monitor agreement statuses across the full portfolio to catch contracts approaching expiration
* Use the Agreements entity to build a renewal calendar in Google Sheets or Looker Studio
* Tag contracts by type or counterparty, then filter in your destination to prioritize reviews
{% endtab %}
{% tab title="Finance" %}
* Pull agreement data alongside financial records to match contract obligations with budget items
* Use Aggregate transformations to count active agreements by type or counterparty for spend analysis
* Track contract creation trends over time using the created date field in Reports
{% endtab %}
{% tab title="Operations" %}
* Audit organization members and their roles to ensure access permissions are appropriate
* Use the Folders entity to validate that contracts are organized consistently
* Feed Agreements data into ChatGPT or Claude to generate contract summaries or flag missing terms
{% endtab %}
{% endtabs %}
## Platform-specific notes
* Concord's API is accessed via API key — OAuth is not supported
* The Reports entity returns Concord's own pre-built report data, not raw event logs
* Nested folder structures are represented via parent folder IDs — you'll need to join the Folders entity to itself to reconstruct the hierarchy
* Tag and folder associations are stored on the Agreements entity, making it the natural center for most joins
## Concord common issues
### Connection issues
My API key is rejected and the data flow won't connect
Double-check that you've copied the full API key from Concord — partial keys are a common cause. You can find your API key under **Settings > API** in your Concord account. Also confirm that API access is enabled for your account tier; some Concord plans restrict API usage.
The data flow fails immediately after setup
This usually points to a connectivity issue between Coupler.io and the Concord API. Try re-entering your API key in the source settings to rule out a copy-paste error. If the problem persists, check Concord's status page for any active incidents.
### Missing data
Some agreements aren't showing up in my export
Concord's API only returns records that your API key's account has permission to access. If agreements belong to a different organization or folder that your account can't read, they'll be silently excluded. Check whether the missing agreements are in a restricted folder or owned by another org.
The Reports entity returns no data or very few rows
The Reports entity returns Concord's pre-built reports, which must exist in your account before they appear here. If you haven't created any reports inside Concord, this entity will be empty. Create or save a report in Concord first, then re-run the data flow.
Tags or folder associations are missing from agreements
Tags and folder data are separate entities that link to agreements by ID. If you're looking for this data in the Agreements entity alone, it will appear as IDs rather than names. Pull the Tags and Folders entities separately and use a Join transformation in Coupler.io to enrich your agreements with the full labels.
### Permission errors
I get a 403 or "insufficient permissions" error on certain entities
This means the account associated with your API key doesn't have read access to that entity. In Concord, check that the user account tied to your API key has the appropriate role — admin or owner-level access is typically required to read organization-wide data like Organization members or User organizations.
### Data discrepancies
Agreement counts in Coupler.io don't match what I see in the Concord UI
The Concord UI may show agreements from multiple organizations if you're a member of several. Your API key is scoped to a specific organization, so it only returns agreements from that org. If you need data from multiple orgs, create separate data flows with API keys for each organization and use an Append transformation to combine them.
### Rate limits
My data flow is slow or times out on large agreement sets
Concord's API enforces rate limits that can slow down syncs when you have a large number of agreements. If you're hitting delays, try scheduling syncs during off-peak hours or splitting large pulls across multiple data flows by entity. Coupler.io's Airbyte-based connector handles pagination automatically, but very large datasets will still take longer.
## Concord FAQ
Can I connect multiple Concord organizations to Coupler.io?
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.
Which Concord entities are available in Coupler.io?
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.
Where do I find my Concord API key?
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.
Does Coupler.io support incremental sync for Concord?
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.
Can I use Concord data with AI tools like ChatGPT or Claude?
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.
Why do tag names show up as IDs in my Agreements data?
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.
How do I track contracts that are expiring soon?
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.
{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](#concord-data-overview) article. If you're running into sync errors or missing records, check [Common Issues](#concord-common-issues) 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.coupler.io/sources/category/finance-and-accounting/concord.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.