--- title: "Connect Buildkite and Quo - APIANT.ai" description: "When \"New build\" fires in Buildkite, your agent runs \"Add contact\" in Quo, or \"List Phone Numbers\" in Quo to \"Add annotation\" in Buildkite." canonical: "https://apiant.ai/connect/buildkite-to-quo" --- # Connect Buildkite and Quo When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Add contact** in [Quo](https://apiant.ai/connections/quo), or **List Phone Numbers** in Quo 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 Quo **1** trigger Quo **21** 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 Quo 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 Quo can do together ### From Buildkite to Quo - When **New build** in Buildkite then **Add contact** in Quo - When **Build finished** in Buildkite then **Add task** in Quo ### From Quo to Buildkite - When **List Phone Numbers** in Quo then **Add annotation** in Buildkite - When **List Phone Numbers** in Quo 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 Quo ## Triggers and actions 3 triggers · 33 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 **List Phone Numbers** Triggers when a new phone number is added to your Quo workspace. - Action **Add contact** Adds a new contact to your Quo workspace, with name, company, role, emails, phone numbers and custom field values. - Action **Add task** Creates a task in Quo linked to a phone number, a conversation, or a conversation activity, optionally with a due date and an assigned user. - Action **Delete contact** Deletes a contact from your Quo workspace. - Action **Get a Message by ID** Returns a single text message by its ID, including its sender, recipients, content, direction, delivery status and any attached media. - Action **Get a Summary for a Call** Returns the AI-generated summary of a call, including key points discussed, suggested next steps, and any Sona job results. Call summaries are available on Business and Scale plans. - Action **Get a Transcription for a Call** Returns the transcript of a call, including each spoken segment with its speaker and timing. Transcripts are available on Quo Business and Scale plans. - Action **Get call** Returns a single Quo call by its ID, including its direction, status, participants, duration and timestamps. - Action **Get contact** Returns a single Quo contact by its ID, including name, company, role, phone numbers, emails and custom field values. - Action **Get phone number** Returns one of your Quo phone numbers, including its display name, number, forwarding setting, assigned users and calling/messaging restrictions. - Action **Get Recordings for a Call** Returns the recordings for a call, oldest segment first, with each recording's status, duration, file type and download URL. - Action **Get user** Returns a user in your Quo workspace, including their name, email, role and profile picture. - Action **Get voicemail for a call** Returns the voicemail left on a call, including its status, length, transcript and a link to the audio. Fields stay blank while the voicemail is still processing. - Action **List Calls** Returns the calls between one of your Quo numbers and a specific external phone number, optionally limited to a date range. - Action **List contacts** Returns the contacts in your Quo workspace, optionally limited to contacts with specific external IDs or sources. - Action **List Conversations** Returns the conversations in your Quo workspace, newest activity first, optionally narrowed to specific Quo numbers, a user's access, or a created/updated date range. - Action **List Messages** Returns the text messages exchanged between one of your Quo numbers and the given participants, newest first, optionally filtered by sender and date range. - Action **List Phone Numbers** Returns the phone numbers in your Quo workspace along with the users who have access to each, optionally limited to one user's numbers. - Action **List tasks** Returns the tasks in your Quo workspace, including title, description, due date, assignee and completion status. - Action **List users** Returns every user in your Quo workspace, with their email, name, role and picture. - Action **Send a Message** Sends a text message from one of your Quo phone numbers to up to 10 recipients. - Action **Update contact** Updates an existing Quo contact's name, company, role, emails, phone numbers and custom fields. Fields you leave blank keep their current values. ## 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) - [ **Quo** Quo is a next-generation phone system to engage customers, collaborate with your team, and scale your reach...](https://apiant.ai/connections/quo) 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 Quo - [ **HubSpot to Quo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-quo) - [ **Google Sheets to Quo** Google Sheets](https://apiant.ai/connect/google-sheets-to-quo) - [ **Gmail to Quo** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-quo) - [ **Google Calendar to Quo** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-quo) - [ **Google Drive to Quo** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-quo) - [ **Mailchimp to Quo** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-quo) Questions ## Buildkite and Quo, 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 Quo when something happens in Buildkite? Any of Quo's 21 actions, including Send a Message, Update contact, Add contact and Add task. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Quo to Buildkite? Yes. When something happens in Quo, your agent can act in Buildkite too. This page covers both directions: Quo's triggers and Buildkite's actions are listed here as well. ### ### Do I have to build a connector for Buildkite or Quo? 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 Quo 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.