Integration
Connect Buildkite and Concord CLM
When New build fires in Buildkite, your agent runs Create a New Document From a Template in Concord CLM, or New agreement in Concord CLM to Add annotation in Buildkite. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Buildkite and Concord CLM to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Buildkite and Concord CLM can do together
From Buildkite to Concord CLM
When New build in Buildkite
then Create a New Document From a Template in Concord CLM
When Build finished in Buildkite
then Create an Executed Document in Concord CLM
From Concord CLM to Buildkite
When New agreement in Concord CLM
then Add annotation in Buildkite
When New agreement in Concord CLM
then Add build in Buildkite
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 Buildkite and Concord CLM
Triggers and actions 3 triggers · 30 actions
Trigger
Build finishedTriggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).
Trigger
New buildTriggers when a new build is scheduled in a Buildkite pipeline.
Action
Add annotationCreates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.
Action
Add buildCreates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.
Action
Add pipelineCreates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.
Action
Cancel buildCancels a running or scheduled build in a Buildkite pipeline and returns the updated build.
Action
Delete pipelinePermanently deletes a pipeline from your Buildkite organization.
Action
Get buildReturns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.
Action
Get pipelineReturns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.
Action
List agentsReturns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.
Action
List buildsReturns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.
Action
List pipelinesReturns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.
Action
Rebuild buildStarts a new build that re-runs an existing build of a pipeline, and returns the new build.
Action
Update pipelineUpdates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.
Trigger
New agreementTriggers when a new agreement appears in the selected Concord organization.
Action
Add agreementCreates 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 attachmentUploads a file and attaches it to a Concord agreement, and returns the ID of the new attachment.
Action
Add folderCreates a new folder inside an existing folder of a Concord organization and returns the new folder.
Action
Add member to agreementInvites 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 TemplateCreates a new Concord document from an automated template, filling in its variables and optionally inviting people to it.
Action
Create an Executed DocumentCreates 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 ApprovedCreates a Concord webhook integration that calls the given URL when an agreement is fully approved.
Action
Create webhook - Document Fully SignedCreates a Concord webhook integration that calls the given address when an agreement is fully signed.
Action
Create webhook - Signature ProvidedCreates a Concord webhook integration that calls the given address whenever a new signature is added to an agreement.
Action
Delete agreementPermanently deletes an agreement from a Concord organization.
Action
Get agreementReturns 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 agreementsReturns the agreements in a Concord organization's inbox, filtered by stage and optionally by creator, tags, dates, parties and search text.
Action
List automated templatesReturns the automated templates available in a Concord organization, with each template's id, title and description.
Action
List foldersReturns the folder tree of a Concord organization: the root folder with its nested subfolders, access settings and document counts.
Action
List organizationsReturns every Concord organization the connected user belongs to, including each organization's name, subscription, and the user's role in it.
Action
Move agreementMoves an agreement into a different folder in a Concord organization.
Action
Request signatureRequests 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 agreementUpdates the status of an existing Concord agreement, setting it to Signing or Broken.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Buildkite
Buildkite to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Buildkite to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Buildkite to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Buildkite to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Buildkite to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Buildkite to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Concord CLM
ActiveCampaign to Concord CLMActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Concord CLMOrganize anything with Airtable, a modern database created for everyone.
Asana to Concord CLMAsana is a collaborative information manager for workspace.
ClickUp to Concord CLMClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to Concord CLMBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to Concord CLMCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Buildkite and Concord CLM, answered
What can start an automation from Buildkite?
Any of Buildkite's 2 triggers in the catalog, including New build and Build finished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Concord CLM when something happens in Buildkite?
Any of Concord CLM's 18 actions, including Create a New Document From a Template, Create an Executed Document, Create webhook - Document Fully Approved and Create webhook - Document Fully Signed. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Concord CLM to Buildkite?
Yes. When something happens in Concord CLM, your agent can act in Buildkite too. This page covers both directions: Concord CLM's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Concord CLM?
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 Buildkite and Concord CLM 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.