Integration
Connect BugBug and Buildkite
When Any Cloud Suite Run Failed fires in BugBug, your agent runs Add annotation in Buildkite, or New build in Buildkite to Run Suite in BugBug. 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 BugBug and Buildkite 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 BugBug and Buildkite can do together
From BugBug to Buildkite
When Any Cloud Suite Run Failed in BugBug
then Add annotation in Buildkite
When Any Cloud Suite Run Passed in BugBug
then Add build in Buildkite
From Buildkite to BugBug
When New build in Buildkite
then Run Suite in BugBug
When Build finished in Buildkite
then Run Test in BugBug
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 BugBug and Buildkite
Triggers and actions 8 triggers · 20 actions
Trigger
Any Cloud Suite Run FailedTriggers when a suite run in the BugBug cloud fails. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Cloud Suite Run PassedTriggers when a suite run in the BugBug cloud passes. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Cloud Suite Run StartedTriggers when a suite starts running in the BugBug cloud. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Failed in the CloudTriggers when a test run in the BugBug cloud fails. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Passed in the CloudTriggers when a test run in the BugBug cloud passes. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Started in the CloudTriggers when a test starts running in the BugBug cloud. Returns the run's name, status, timing and a link to it in BugBug.
Action
Get Suite RunReturns one BugBug suite run with its status, timing and error code.
Action
Get Test RunReturns one BugBug test run with its status, timing and error code.
Action
List SuitesReturns the suites in the BugBug project, optionally filtered by name.
Action
List TestsReturns the tests in the BugBug project, optionally filtered by name.
Action
Run SuiteStarts a cloud run of a BugBug suite and returns the new run's ID, status and link.
Action
Run TestStarts a cloud run of a BugBug test and returns the new run's ID, status and link.
Action
Stop Suite RunStops a running BugBug suite run and returns its status.
Action
Stop Test RunStops a running BugBug test run and returns its status.
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.
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 BugBug
BugBug to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BugBug to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BugBug to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BugBug to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BugBug to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BugBug to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Buildkite
Asana to BuildkiteAsana is a collaborative information manager for workspace.
ActiveCampaign to BuildkiteActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to BuildkiteOrganize anything with Airtable, a modern database created for everyone.
Brevo to BuildkiteBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
100Hires ATS to Buildkite100Hires ATS is a recruitment software that includes talent sourcing, and applicant tracking to accelerate...
2Chat to Buildkite2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
Questions
BugBug and Buildkite, answered
What can start an automation from BugBug?
Any of BugBug's 6 triggers in the catalog, including Any Cloud Suite Run Failed, Any Cloud Suite Run Passed, Any Cloud Suite Run Started and Any Test Failed in the Cloud. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Buildkite when something happens in BugBug?
Any of Buildkite's 12 actions, including Update pipeline, Add annotation, Add build and Add pipeline. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Buildkite to BugBug?
Yes. When something happens in Buildkite, your agent can act in BugBug too. This page covers both directions: Buildkite's triggers and BugBug's actions are listed here as well.
Do I have to build a connector for BugBug or Buildkite?
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 BugBug and Buildkite 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.