Integration
Connect Buildkite and Chaport
When New build fires in Buildkite, your agent runs Send a Message in Chaport, or Chat Stage Updated (instant) in Chaport 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 Chaport 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 Chaport can do together
From Buildkite to Chaport
When New build in Buildkite
then Send a Message in Chaport
When Build finished in Buildkite
then Create an Operator in Chaport
From Chaport to Buildkite
When Chat Stage Updated (instant) in Chaport
then Add annotation in Buildkite
When New Chat Started in Chaport
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 Chaport
Triggers and actions 10 triggers · 24 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
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
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
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 Chaport
aikstockdata to ChaportKOSPI/KOSDAQ/KONEX daily settled closes, DART filings with receipt times, quarterly earnings
ActiveCampaign to ChaportActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ChaportOrganize anything with Airtable, a modern database created for everyone.
Asana to ChaportAsana is a collaborative information manager for workspace.
Freshdesk to ChaportFreshdesk is a cloud-based customer support and helpdesk platform.
Brevo to ChaportBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Buildkite and Chaport, 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 Chaport when something happens in Buildkite?
Any of Chaport's 12 actions, including Create an Operator, Send a Message, Update an Operator and Update a Visitor. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Chaport to Buildkite?
Yes. When something happens in Chaport, your agent can act in Buildkite too. This page covers both directions: Chaport's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Chaport?
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 Chaport 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.