---
title: "Connect Concord CLM and Request Tracker (RT) - APIANT.ai"
description: "When \"New agreement\" fires in Concord CLM, your agent runs \"Create Ticket\" in Request Tracker (RT)."
canonical: "https://apiant.ai/connect/concord-clm-to-request-tracker-rt"
---

# Connect Concord CLM and Request Tracker (RT)

When **New agreement** fires in [Concord CLM](https://apiant.ai/connections/concord-clm), your agent runs **Create Ticket** in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), or **Ticket Created** in Request Tracker (RT) to **Create a New Document From a Template** in Concord CLM. Describe the whole flow and it is built, tested on every scenario and kept running.

Concord CLM **1** trigger Concord CLM **18** actions Request Tracker (RT) **3** triggers Request Tracker (RT) **18** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Concord CLM and Request Tracker (RT) to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Concord CLM and Request Tracker (RT) can do together

### From Concord CLM to Request Tracker (RT)

- When **New agreement** in Concord CLM then **Create Ticket** in Request Tracker (RT)
- When **New agreement** in Concord CLM then **Update ticket** in Request Tracker (RT)

### From Request Tracker (RT) to Concord CLM

- When **Ticket Created** in Request Tracker (RT) then **Create a New Document From a Template** in Concord CLM
- When **Ticket Status Changed** in Request Tracker (RT) then **Create an Executed Document** in Concord CLM

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Concord CLM and Request Tracker (RT)

## Triggers and actions 4 triggers · 36 actions

- Trigger

**New agreement**

Triggers when a new agreement appears in the selected Concord organization.

- Action

**Add agreement**

Creates a new agreement in a Concord organization, either as a blank draft, template or contract, or from an existing template or contract. Returns the new agreement's identifiers.

- Action

**Add attachment**

Uploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment.

- Action

**Add folder**

Creates a new folder inside an existing folder of a Concord organization and returns the new folder.

- Action

**Add member to agreement**

Invites a person to an agreement by email with the chosen permission level and sends them an invitation message. Returns the agreement's id, unique identifier and status.

- Action

**Create a New Document From a Template**

Creates a new Concord document from an automated template, filling in its variables and optionally inviting people to it.

- Action

**Create an Executed Document**

Creates an agreement in Concord with the status of an executed contract, rather than a draft or template. Returns the new agreement's identifiers.

- Action

**Create webhook - Document Fully Approved**

Creates a Concord webhook integration that calls the given URL when an agreement is fully approved.

- Action

**Create webhook - Document Fully Signed**

Creates a Concord webhook integration that calls the given address when an agreement is fully signed.

- Action

**Create webhook - Signature Provided**

Creates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement.

- Action

**Delete agreement**

Permanently deletes an agreement from a Concord organization.

- Action

**Get agreement**

Returns one Concord agreement by its UID, including its title, status, folder, tags, permission and creation details. An error occurs if the agreement is not found.

- Action

**List agreements**

Returns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text.

- Action

**List automated templates**

Returns the automated templates available in a Concord organization, with each template's id, title and description.

- Action

**List folders**

Returns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts.

- Action

**List organizations**

Returns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it.

- Action

**Move agreement**

Moves an agreement into a different folder in a Concord organization.

- Action

**Request signature**

Requests signatures on an agreement from its signers. Colleagues are added to the agreement, external signers are emailed an invitation, and when a signing order is enabled the request goes to the next signer in that order.

- Action

**Update agreement**

Updates the status of an existing Concord agreement, setting it to Signing or Broken.

- Trigger

**Ticket Correspondence**

Triggers when a ticket is replied to (that is, corresponded with).

- Trigger

**Ticket Created**

Triggers when a new Request Tracker ticket is created.

- Trigger

**Ticket Status Changed**

Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.

- Action

**Add asset**

Create an asset.

- Action

**Comment on a Ticket**

Add an internal comment to a ticket and send to any internal watchers.

- Action

**Create Ticket**

Create a new ticket in Request Tracker.

- Action

**Find Attachment**

Locate an attachment by ID.

- Action

**Find Ticket**

Locate a ticket by ID.

- Action

**Find Tickets**

Issue a query to find matching tickets.

- Action

**Find Transaction**

Find a transaction by ID

- Action

**Get asset**

Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.

- Action

**Get queue**

Get a queue by id or name.

- Action

**Get user**

Get a user by id or name.

- Action

**List queues**

List all queues visible to user.

- Action

**List ticket history**

List transactions of a ticket.

- Action

**Reply to a Ticket**

Reply to the requestor and any internal or external watchers of a ticket.

- Action

**Update ticket**

General ticket update (Owner, Priority, Queue, custom fields).

- Action

**Update Ticket Due Date**

Update the due date of a ticket.

- Action

**Update Ticket Status**

Update the status of a ticket.

- Action

**Update Ticket Subject**

Update the subject of a ticket.

- Action

**Update user**

Update a user.

## Each app on its own

- [ **Concord CLM** Concord is a full contract lifecycle management platform with drafting, approvals, e-signature and storage -...](https://apiant.ai/connections/concord-clm)
- [ **Request Tracker (RT)** Request Tracker (RT) is an open-source, enterprise-grade ticketing system.](https://apiant.ai/connections/request-tracker-rt)

Reviews

## What our customers say

## More from Concord CLM

- [ **Concord CLM to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/concord-clm-to-hubspot)
- [ **Concord CLM to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/concord-clm-to-salesforce)
- [ **Concord CLM to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/concord-clm-to-slack)
- [ **Concord CLM to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/concord-clm-to-google-sheets)
- [ **Concord CLM to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/concord-clm-to-gmail)
- [ **Concord CLM to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/concord-clm-to-google-calendar)

## More into Request Tracker (RT)

- [ **HubSpot to Request Tracker (RT)** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-request-tracker-rt)
- [ **Google Sheets to Request Tracker (RT)** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-request-tracker-rt)
- [ **Gmail to Request Tracker (RT)** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-request-tracker-rt)
- [ **Google Calendar to Request Tracker (RT)** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-request-tracker-rt)
- [ **Google Drive to Request Tracker (RT)** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-request-tracker-rt)
- [ **Mailchimp to Request Tracker (RT)** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-request-tracker-rt)

Questions

## Concord CLM and Request Tracker (RT), answered

###

### What can start an automation from Concord CLM?

Any of Concord CLM's 1 trigger in the catalog, including New agreement. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Request Tracker (RT) when something happens in Concord CLM?

Any of Request Tracker (RT)'s 18 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Request Tracker (RT) to Concord CLM?

Yes. When something happens in Request Tracker (RT), your agent can act in Concord CLM too. This page covers both directions: Request Tracker (RT)'s triggers and Concord CLM's actions are listed here as well.

###

### Do I have to build a connector for Concord CLM or Request Tracker (RT)?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Concord CLM and Request Tracker (RT) without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
