Integration
Connect Buildkite and Campaign Monitor
When New build fires in Buildkite, your agent runs Add campaign in Campaign Monitor, or New client in Campaign Monitor 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 Campaign Monitor 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 Campaign Monitor can do together
From Buildkite to Campaign Monitor
When New build in Buildkite
then Add campaign in Campaign Monitor
When Build finished in Buildkite
then Add custom field in Campaign Monitor
From Campaign Monitor to Buildkite
When New client in Campaign Monitor
then Add annotation in Buildkite
When New list in Campaign Monitor
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 Campaign Monitor
Triggers and actions 5 triggers · 33 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 clientPolling trigger. Fires when a new client is added to the account.
Trigger
New listPolling trigger. Fires when a new list is added to the specified client.
Trigger
New subscriberPolling trigger. Fires when a new active subscriber is added to the specified list.
Action
Add campaignCreate a draft campaign.
Action
Add custom fieldAdds a custom field to the specified list. An error occurs if the custom field name already exists.
Action
Add or update subscriberAdds a subscriber to the specified list if the email is not found, otherwise updates the existing subscriber.
Action
Create listCreates a new subscriber list for the specified client.
Action
Delete custom fieldDeletes a custom field from the specified list.
Action
Delete listDelete a list.
Action
Delete subscriberDelete a subscriber from a list.
Action
Get listGet details of a list.
Action
Get subscriberRetrieves a subscriber's details (including custom fields and state) by email from the specified list.
Action
List campaignsList sent campaigns for a client.
Action
List clientsList clients in the account.
Action
List custom fieldsLists a list's custom fields: field name, key, data type, options and preference-center visibility.
Action
List draft campaignsLists a client's draft (unsent) campaigns.
Action
List listsList all subscriber lists for a client.
Action
List segmentsList segments for a list.
Action
List subscribersList active subscribers of a list (paginated).
Action
UnsubscribeRemoves a subscriber from the specified list.
Action
Update custom fieldUpdates a custom field in the specified list. An error occurs if the custom field name is not found.
Action
Update custom field optionsUpdates a custom field's options in the specified list. An error occurs if the custom field name is not found.
Action
Update listUpdate list settings.
Action
Update subscriber multi-select fieldUpdates a subscriber's multi-select custom field. Existing selected values can be retained or replaced.
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 Campaign Monitor
ActiveCampaign to Campaign MonitorActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Campaign MonitorOrganize anything with Airtable, a modern database created for everyone.
Asana to Campaign MonitorAsana is a collaborative information manager for workspace.
Brevo to Campaign MonitorBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to Campaign MonitorCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
2Chat to Campaign Monitor2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
Questions
Buildkite and Campaign Monitor, 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 Campaign Monitor when something happens in Buildkite?
Any of Campaign Monitor's 21 actions, including Create list, Update custom field, Update custom field options and Update list. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Campaign Monitor to Buildkite?
Yes. When something happens in Campaign Monitor, your agent can act in Buildkite too. This page covers both directions: Campaign Monitor's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Campaign Monitor?
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 Campaign Monitor 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.