> 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

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 %}

## Available entities

| Entity               | Description                                     |
| -------------------- | ----------------------------------------------- |
| Agreements           | Contract agreements, terms, status, and details |
| Organizations        | Organization details and settings               |
| Organization members | Members and their access permissions            |
| User organizations   | User associations with organizations and roles  |
| Folders              | Folder structure for contract organization      |
| Reports              | Contract and business reports with analytics    |
| Tags                 | Tags used to categorize and organize contracts  |


---

# 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.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.