--- title: "Connect Concord CLM and JIRA - APIANT.ai" description: "When \"New agreement\" fires in Concord CLM, your agent runs \"Add Comment to Issue\" in JIRA." canonical: "https://apiant.ai/connect/concord-clm-to-jira" --- # Connect Concord CLM and JIRA When **New agreement** fires in [Concord CLM](https://apiant.ai/connections/concord-clm), your agent runs **Add Comment to Issue** in [JIRA](https://apiant.ai/connections/jira), or **New Issue** in JIRA 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 JIRA **2** triggers JIRA **138** 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 JIRA 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 JIRA can do together ### From Concord CLM to JIRA - When **New agreement** in Concord CLM then **Add Comment to Issue** in JIRA - When **New agreement** in Concord CLM then **Add comment** in JIRA ### From JIRA to Concord CLM - When **New Issue** in JIRA then **Create a New Document From a Template** in Concord CLM - When **New or Updated Issue** in JIRA 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 JIRA ## Triggers and actions 3 triggers · 156 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 **New Issue** Polls for newly created issues in a project (ordered by creation date). - Trigger **New or Updated Issue** Polls for issues created or updated recently (ordered by updated date). - Action **Add attachment** add an attachment to an issue - Action **Add comment** add a comment to an issue - Action **Add Comment to Issue** Adds a comment to the specified issue. - Action **Add filter as favorite** Add filter as favorite - Action **Add gadget to dashboard** Add gadget to dashboard - Action **Add user to group** add a user to a group - Action **Add vote** add the current user's vote to an issue - Action **Add worklog** add a worklog to an issue - Action **Archive issues by ID or key** archive issues by ID/key - Action **Archive issue(s) by JQL** Archive issue(s) by JQL - Action **Assign Issue** Assigns an issue to a user by account ID. - Action **Bulk create issue** bulk create issues - Action **Bulk create statuses** Bulk create statuses - Action **Bulk delete issues** bulk delete issues - Action **Bulk delete Statuses** Bulk delete Statuses - Action **Bulk delete worklogs** bulk delete worklogs on an issue - Action **Bulk edit dashboards** Bulk edit dashboards - Action **Bulk edit issues** bulk edit issue fields - Action **Bulk fetch issues** bulk fetch issues by ID/key - Action **Bulk move issues** bulk move issues - Action **Bulk move worklogs** bulk move worklogs - Action **Bulk transition issue statuses** bulk transition issue statuses - Action **Bulk unwatch issues** bulk unwatch issues - Action **Bulk watch issues** bulk watch issues - Action **Change filter owner** Change filter owner - Action **Copy dashboard** Copy dashboard - Action **Create component** Create component - Action **Create custom field** Create custom field - Action **Create dashboard** Create dashboard - Action **Create filter** Create filter - Action **Create group** Create group - Action **Create Issue** Creates a new issue in the specified project. - Action **Create issue link** create a link between two issues - Action **Create issue link type** create an issue link type - Action **Create issue type** create an issue type - Action **Create project** create a project - Action **Create project category** create a project category - Action **Create related work** Create related work - Action **Create user** create a user - Action **Create version** Create version - Action **Delete and replace version** Delete and replace version - Action **Delete attachment** delete an attachment - Action **Delete comment** delete a comment - Action **Delete component** Delete component - Action **Delete custom field** Delete custom field - Action **Delete dashboard** Delete dashboard - Action **Delete filter** Delete filter - Action **Delete Issue** Deletes an issue by its key or ID. - Action **Delete issue link** delete an issue link - Action **Delete issue link type** delete an issue link type - Action **Delete issue type** delete an issue type - Action **Delete project** delete a project - Action **Delete project asynchronously** delete a project asynchronously - Action **Delete project category** delete a project category - Action **Delete related work** Delete related work - Action **Delete user** delete a user - Action **Delete version** Delete version - Action **Delete vote** remove the current user's vote from an issue - Action **Delete watcher** remove a watcher from an issue - Action **Delete worklog** delete a worklog - Action **Export Archived Issues** Export archived issue(s) - Action **Get all dashboards** Get all dashboards - Action **Get all projects** Get all projects - Action **Get attachment content** get attachment content - Action **Get attachment metadata** get attachment metadata - Action **Get available transitions** Get available transitions - Action **Get bulk available transitions** get transitions available for bulk transition - Action **Get comment** get a single comment - Action **Get comments by IDs** get comments by IDs - Action **Get component** Get component - Action **Get create issue metadata** Get create issue metadata - Action **Get create metadata issue types for a project** get create-metadata issue types for a project - Action **Get custom field** Fetches a custom field's definition by its ID, including its name, description and field type. Returns found = false when no field has that ID. - Action **Get dashboard** Get dashboard - Action **Get edit issue metadata** get edit metadata for an issue - Action **Get favorite filters** Get favorite filters - Action **Get filter** Get filter - Action **Get group** Get group - Action **Get Issue** Returns the details of a single issue by its key or ID. - Action **Get Issue Comments** Returns all comments for the specified issue. - Action **Get issue link** get an issue link - Action **Get issue link type** get an issue link type - Action **Get issue link types** list issue link types - Action **Get Issue Transitions** Returns the workflow transitions available for the specified issue. - Action **Get issue type** get an issue type - Action **Get issue watchers** get watchers of an issue - Action **Get issue worklogs** get worklogs on an issue - Action **Get is watching issue bulk** check watching status for multiple issues - Action **Get my filters** Get my filters - Action **Get Project** Returns the details of a single project by its key or ID. - Action **Get project category** Fetches a project category by ID, with its name and description. An error occurs if the category is not found. - Action **Get project components** get all components of a project - Action **Get project versions** get all versions of a project - Action **Get recent projects** get recently viewed projects - Action **Get related work** Get related work - Action **Get status** Get status - Action **Get status category** Get status category - Action **Get transitions** get available transitions for an issue - Action **Get user** get a user - Action **Get user groups** get groups a user belongs to - Action **Get users from group** list members of a group - Action **Get version** Get version - Action **Get votes** get votes on an issue - Action **Get worklog** get a worklog - Action **Get worklogs by IDs** get worklogs by IDs - Action **Get worklogs by issue ID and worklog ID** get worklogs by issue ID and worklog ID (internal) - Action **List Project Issue Types** Returns the issue types available, optionally for a given project. - Action **List Projects** Returns a paginated list of projects visible to the user. - Action **List users** Lists the users visible to the connected Jira account. Takes no search criterion. - Action **Merge versions** merge one version into another - Action **Move version** Move version - Action **Remove filter as favorite** Remove filter as favorite - Action **Remove gadget from dashboard** Remove gadget from dashboard - Action **Remove group** Remove group - Action **Remove user from group** remove a user from a group - Action **Restore custom field from trash** Restore custom field from trash - Action **Restore deleted or archived project** restore a deleted or archived project - Action **Search for dashboards** Search for dashboards - Action **Search for filters** Search for filters - Action **Search for issues using JQL enhanced search (GET)** Search for issues using JQL enhanced search (GET) - Action **Search for issues using JQL enhanced search (POST)** search for issues using enhanced JQL (POST) - Action **Search Issues (JQL)** Searches for issues using a JQL query. - Action **Transition Issue** Moves an issue to a new status by performing a workflow transition. - Action **Unarchive issues by keys or ID** unarchive issues by key/ID - Action **Update comment** update a comment - Action **Update component** Update component - Action **Update custom field** Update custom field - Action **Update dashboard** Update dashboard - Action **Update filter** Update filter - Action **Update gadget on dashboard** Update gadget on dashboard - Action **Update Issue** edit an issue - Action **Update issue link type** update an issue link type - Action **Update issue type** update an issue type - Action **Update project** update a project - Action **Update project category** update a project category - Action **Update related work** Update one related-work link on a Jira project version. Reads the version's existing related work, overlays only the fields you supply, then writes the merged object back — so anything you leave blank keeps its current value. - Action **Update version** Update version - Action **Update worklog** update a worklog ## 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) - [ **JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connections/jira) 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 JIRA - [ **HubSpot to JIRA** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-jira) - [ **Slack to JIRA** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-jira) - [ **Google Calendar to JIRA** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-jira) - [ **Stripe to JIRA** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/stripe-to-jira) - [ **QuickBooks Online to JIRA** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-jira) - [ **Pipedrive to JIRA** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-jira) Questions ## Concord CLM and JIRA, 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 JIRA when something happens in Concord CLM? Any of JIRA's 138 actions, including Create component, Create custom field, Create dashboard and Create filter. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from JIRA to Concord CLM? Yes. When something happens in JIRA, your agent can act in Concord CLM too. This page covers both directions: JIRA's triggers and Concord CLM's actions are listed here as well. ### ### Do I have to build a connector for Concord CLM or JIRA? 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 JIRA 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.