Integration
Connect Buildkite to KeyNest
When New build fires in Buildkite, your agent runs Add key in KeyNest. 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 KeyNest 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 can start in KeyNest
When New build in Buildkite
then Add key in KeyNest
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 KeyNest
Triggers and actions 2 triggers · 20 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.
- Add key
Adds a new key at a KeyNest Store and returns its drop-off and collection codes.
- Delete collection code
Deletes a KeyNest collection code so it can no longer be used to collect the key.
- Delete key
Deletes a key from your KeyNest account and discards its drop off code. Keys currently stored in a KeyNest location cannot be deleted.
- Get drop off code
Returns the drop-off code for an existing key, along with a link showing the code and the store where the key is dropped off.
- List KeyNest stores
Returns KeyNest locations, optionally narrowed by country, city, location type, nearby point, address or a single store.
- List keys
Returns all keys on the KeyNest account, with each key's details and current status.
- List offices
Returns every office on your KeyNest account, with each office's id, name and your access level.
- Update key
Updates the name, address, property reference or notes on an existing KeyNest key.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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 KeyNest
Questions
Buildkite and KeyNest, 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 KeyNest when something happens in Buildkite?
Any of KeyNest's 8 actions, including Update key, Add key, Get drop off code and List KeyNest stores. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from KeyNest to Buildkite?
KeyNest has no triggers in the catalog today, so automations start in Buildkite. If you need the other direction, ask: your agent reads KeyNest's API documentation and adds it.
Do I have to build a connector for Buildkite or KeyNest?
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 KeyNest 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.