Integration
Connect Buildkite and Hellotracks
When New build fires in Buildkite, your agent runs Add member in Hellotracks, or Completed Job in Hellotracks 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 Hellotracks to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Hellotracks can do together
From Buildkite to Hellotracks
When New build in Buildkite
then Add member in Hellotracks
When Build finished in Buildkite
then Add place in Hellotracks
From Hellotracks to Buildkite
When Completed Job in Hellotracks
then Add annotation in Buildkite
When New Job in Hellotracks
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 Hellotracks
Triggers and actions 7 triggers · 31 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
Alert triggeredFires when a configured alert (late arrival, idle, zone entry/exit, low battery, etc.) triggers. Webhook key alert_triggered via /v1/webhooks or /api/setwebhooks (Hellotracks API).
Trigger
Completed JobTriggers when a job reaches a completed state.
Trigger
Member clocked in or outFires when a worker turns location tracking on (clock-in) or off (clock-out) from the mobile app. Webhook key clock_in_out via /v1/webhooks or /api/setwebhooks (Hellotracks API).
Trigger
New JobTriggers when a job is created.
Trigger
Updated JobTriggers when a job is created, assigned, completed, archived, or otherwise updated.
Action
Add memberCreate a new team member (worker) account.
Action
Add placeCreate a new saved place/geofence.
Action
Archive JobArchives a job by ID.
Action
Auto-assign jobsAutomatically assign a set of unassigned jobs to available members.
Action
Create JobCreates or updates a job. If External ID matches an existing job, the existing job is updated.
Action
Delete JobDeletes a job by ID.
Action
Delete memberDelete a team member account.
Action
Distribute jobAssign/distribute one or more jobs to members for dispatch.
Action
Find JobFinds a job by External ID.
Action
Find MemberFinds a member by exact email, username, name, or UID.
Action
Generate reportGenerate a report (e.g. timesheet/activity) for a date range.
Action
Get companyGet the authenticated company account's profile/settings.
Action
List placesGet the company's saved places/geofences.
Action
Locate memberGet a member's current/last known GPS location.
Action
Optimize routeCompute an optimized route ordering for a member's assigned jobs.
Action
Restore jobRestore a previously archived job.
Action
Update JobUpdates a job by ID.
Action
Update memberEdit an existing team member's fields.
Action
Update placeEdit an existing saved place/geofence.
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 Hellotracks
Google Sheets to HellotracksGoogle Sheets
Gmail to HellotracksGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HellotracksGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to HellotracksGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HellotracksActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to HellotracksOrganize anything with Airtable, a modern database created for everyone.
Questions
Buildkite and Hellotracks, 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 Hellotracks when something happens in Buildkite?
Any of Hellotracks's 19 actions, including Create Job, Update Job, Update member and Update place. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hellotracks to Buildkite?
Yes. When something happens in Hellotracks, your agent can act in Buildkite too. This page covers both directions: Hellotracks's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Hellotracks?
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.
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.