Integration
Connect Buildkite and Pelcro
When New build fires in Buildkite, your agent runs Create Customer in Pelcro, or Customer Created in Pelcro 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 Pelcro 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 Pelcro can do together
From Buildkite to Pelcro
When New build in Buildkite
then Create Customer in Pelcro
From Pelcro to 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 Pelcro
Triggers and actions 7 triggers · 24 actions
- Build finished
Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).
- New build
Triggers when a new build is scheduled in a Buildkite pipeline.
- Add annotation
Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.
- Add build
Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.
- Add pipeline
Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.
- Cancel build
Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.
- Delete pipeline
Permanently deletes a pipeline from your Buildkite organization.
- Get build
Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.
- Get pipeline
Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.
- List agents
Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.
- List builds
Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.
- List pipelines
Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.
- Rebuild build
Starts a new build that re-runs an existing build of a pipeline, and returns the new build.
- Update pipeline
Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.
- Customer Created
Triggers when a user registers via the Pelcro Platform. This means that a customer record exists in Pelcro and has a unique email address, password, and customer ID associated to it.
- Customer Updated
Triggers when a customer is updated in Pelcro.
- Newsletter Created
Triggers when a new newsletter subscription is created in Pelcro.
- Newsletter Updated
Triggers when an existing Pelcro newsletter subscription is updated, such as a change to the subscriber's mailing lists or consent.
- Subscription Created
Triggers when a new subscription is created in Pelcro.
- Add address
Creates a new shipping, billing or primary address for a Pelcro customer.
- Add coupon
Creates a new discount coupon on your Pelcro site, with either a fixed amount or a percentage off.
- Create Customer
Creates a new customer on your Pelcro site.
- Create Newsletter
Creates a newsletter subscriber in Pelcro with their email, signup source and optional consent details.
- Create Plan
Creates a new pricing plan under a Pelcro product, setting its price, currency, billing interval and subscription behavior.
- Create Product
Creates a product in your Pelcro site. Plans and their prices are added under a product.
- Create Subscription
Creates a subscription for a Pelcro customer on a plan, optionally with a coupon, trial period or gift details.
- Get coupon
Returns a single coupon by id, including its code, discount, duration, redemption count and expiration.
- Get newsletter
Returns a single newsletter subscriber by id, including their email, name, lists and consent details.
- List newsletters
Returns newsletter subscribers on your Pelcro site, optionally filtered by exact email address.
- Update customer
Updates an existing Pelcro customer's profile, such as contact details, marketing preferences, password and metadata. Fields left blank are left unchanged.
- Update Newsletter
Updates an existing newsletter subscriber's email, signup source, name, lists and consent details.
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 Pelcro
Google Drive to PelcroGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PelcroMailchimp marketing automation and email platform.
Questions
Buildkite and Pelcro, 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 Pelcro when something happens in Buildkite?
Any of Pelcro's 12 actions, including Create Customer, Create Newsletter, Create Plan and Create Product. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pelcro to Buildkite?
Yes. When something happens in Pelcro, your agent can act in Buildkite too. This page covers both directions: Pelcro's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Pelcro?
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 Pelcro 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.