---
title: "Connect Buildkite and Chaport - APIANT.ai"
description: "When \"New build\" fires in Buildkite, your agent runs \"Send a Message\" in Chaport."
canonical: "https://apiant.ai/connect/buildkite-to-chaport"
---

# Connect Buildkite and Chaport

When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Send a Message** in [Chaport](https://apiant.ai/connections/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.

Buildkite **2** triggers Buildkite **12** actions Chaport **8** triggers Chaport **12** actions

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

## What do you want Buildkite and Chaport 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 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 finished**

Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).

- Trigger

**New build**

Triggers when a new build is scheduled in a Buildkite pipeline.

- Action

**Add annotation**

Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.

- Action

**Add build**

Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.

- Action

**Add pipeline**

Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.

- Action

**Cancel build**

Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.

- Action

**Delete pipeline**

Permanently deletes a pipeline from your Buildkite organization.

- Action

**Get build**

Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.

- Action

**Get pipeline**

Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.

- Action

**List agents**

Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.

- Action

**List builds**

Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.

- Action

**List pipelines**

Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.

- Action

**Rebuild build**

Starts a new build that re-runs an existing build of a pipeline, and returns the new build.

- Action

**Update pipeline**

Updates 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 Finished**

Triggers 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 Started**

Triggers 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 Updated**

Triggers when visitor data is updated.

- Action

**Create an Operator**

Adds a new operator to your Chaport account and returns the created operator.

- Action

**Delete a Message**

Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.

- Action

**Delete an Operator**

Removes an operator from your Chaport account.

- Action

**List Operators**

Returns every operator in your Chaport account, with each operator's name, email, role and status.

- Action

**List Visitors**

Returns the visitors in your Chaport account, one page at a time.

- Action

**Retrieve an Operator**

Returns one Chaport operator with their name, email, role, job title and current status.

- Action

**Retrieve a Visitor**

Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.

- Action

**Retrieve Last Visitor Chat**

Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.

- Action

**Send a Message**

Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.

- Action

**Update an Operator**

Updates a Chaport operator's details. Anything you leave blank keeps its current value.

- Action

**Update a Visitor**

Updates 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 Status**

Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.

## Each app on its own

- [ **Buildkite** Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own...](https://apiant.ai/connections/buildkite)
- [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport)

Reviews

## What our customers say

## More from Buildkite

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

## More into Chaport

- [ **aikstockdata to Chaport** KOSPI/KOSDAQ/KONEX daily settled closes, DART filings with receipt times, quarterly earnings](https://apiant.ai/connect/aikstockdata-to-chaport)
- [ **ActiveCampaign to Chaport** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-chaport)
- [ **Airtable to Chaport** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-chaport)
- [ **Asana to Chaport** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-chaport)
- [ **Freshdesk to Chaport** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/freshdesk-to-chaport)
- [ **Brevo to Chaport** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-chaport)

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.
