Integration
Connect Buildkite and Buttondown
When New build fires in Buildkite, your agent runs Create Email in Buttondown, or New Draft in Buttondown 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 Buttondown 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 Buttondown can do together
From Buildkite to Buttondown
When New build in Buildkite
then Create Email in Buttondown
When Build finished in Buildkite
then Update Email in Buttondown
From Buttondown to Buildkite
When New Draft in Buttondown
then Add annotation in Buildkite
When New Scheduled Email in Buttondown
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 Buttondown
Triggers and actions 6 triggers · 41 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 DraftTriggers when a new draft is created.
Trigger
New Scheduled EmailTriggers when a new email is scheduled.
Trigger
NewslettersTriggers when a new newsletter is created.
Trigger
New TagTriggers when a new tag is created.
Action
Add SegmentCreate a new subscriber segment.
Action
Add SurveyCreate a new survey.
Action
Create DraftCreates a draft.
Action
Create EmailCreates an email.
Action
Create SubscriberCreates a subscriber.
Action
Delete AutomationDelete an automation by id.
Action
Delete EmailDelete an email by id.
Action
Delete NewsletterDelete a newsletter by id.
Action
Delete SegmentDelete a subscriber segment by id.
Action
Delete SubscriberRemove a subscriber by id or email address.
Action
Delete SurveyDelete a survey by id.
Action
Delete TagDelete a tag by id.
Action
Find TagFinds a tag given its name.
Action
Get AutomationRetrieve a single automation by id.
Action
Get EmailRetrieve a single email by id.
Action
Get NewsletterRetrieve a single newsletter by id.
Action
Get SegmentRetrieve a single subscriber segment by id.
Action
Get SurveyRetrieve a single survey by id.
Action
Get TagRetrieve a single tag by id.
Action
List AutomationsList all automations configured on the account.
Action
List SegmentsList all subscriber segments.
Action
List SurveysList all surveys on the account.
Action
Publish EmailPublish a drafted email so it is sent and made public.
Action
Update AutomationUpdate an automation's configuration.
Action
Update EmailUpdate an existing email's content or metadata.
Action
Update NewsletterUpdate a newsletter's settings.
Action
Update SegmentUpdate a subscriber segment's definition.
Action
Update SurveyUpdate a survey's configuration.
Action
Update TagUpdate a tag's name or metadata.
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 Buttondown
ActiveCampaign to ButtondownActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ButtondownOrganize anything with Airtable, a modern database created for everyone.
Asana to ButtondownAsana is a collaborative information manager for workspace.
Brevo to ButtondownBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
2Chat to Buttondown2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
3Scribe to Buttondown3Scribe is the most accurate, automated text transcription available.
Questions
Buildkite and Buttondown, 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 Buttondown when something happens in Buildkite?
Any of Buttondown's 29 actions, including Create Draft, Create Email, Create Subscriber and Update Automation. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Buttondown to Buildkite?
Yes. When something happens in Buttondown, your agent can act in Buildkite too. This page covers both directions: Buttondown's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Buttondown?
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 Buttondown 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.