Integration
Connect Buildkite and Targetprocess
When New build fires in Buildkite, your agent runs Create Build in Targetprocess, or New Bug in Targetprocess 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 Targetprocess 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 Buildkite and Targetprocess can do together
From Buildkite to Targetprocess
When New build in Buildkite
then Create Build in Targetprocess
When Build finished in Buildkite
then Create Task in Targetprocess
From Targetprocess to Buildkite
When New Bug in Targetprocess
then Add annotation in Buildkite
When New Build in Targetprocess
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 Targetprocess
Triggers and actions 13 triggers · 20 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 BugTriggers when a new Bug is added in Targetprocess.
Trigger
New BuildTriggers when a new Build is added in Targetprocess.
Trigger
New CommentTriggers when a new Comment is added in Targetprocess.
Trigger
New FeatureTriggers when a new Feature is added in Targetprocess.
Trigger
New IterationTriggers when a new Iteration is added in Targetprocess.
Trigger
New ReleaseTriggers when a new Release is added in Targetprocess.
Trigger
New RequestTriggers when a new Request is added in Targetprocess.
Trigger
New TaskTriggers when a new Task is added in Targetprocess.
Trigger
New Team IterationTriggers when a new Team Iteration is added in Targetprocess.
Trigger
New TimeTriggers when a new Time record is added in Targetprocess.
Trigger
New User StoryTriggers when a new User Story is added in Targetprocess.
Action
Add Requester to RequestCreates a Requester and attaches them to an existing Request.
Action
Change StateChanges the workflow state of an existing entity.
Action
Create BugCreates a new Bug in a Targetprocess project.
Action
Create BuildCreates a Build in a Targetprocess project.
Action
Create FeatureCreates a Feature, a high-level requirement that groups User Stories.
Action
Create RequestCreates a Request (an idea, issue or question from users).
Action
Create TaskCreates a Task under an existing User Story.
Action
Create User StoryCreates a User Story in a project.
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 ClickhouseColumn-oriented database for real-time analytical SQL queries at petabyte scale.
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...
More into Targetprocess
HubSpot to TargetprocessHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TargetprocessSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TargetprocessSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TargetprocessGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TargetprocessGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TargetprocessGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Buildkite and Targetprocess, 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 Targetprocess when something happens in Buildkite?
Any of Targetprocess's 8 actions, including Create Bug, Create Build, Create Feature and Create Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Targetprocess to Buildkite?
Yes. When something happens in Targetprocess, your agent can act in Buildkite too. This page covers both directions: Targetprocess's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Targetprocess?
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 Targetprocess 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.