Integration
Connect Buildkite and Intervals
When New build fires in Buildkite, your agent runs Add invoice in Intervals, or New client in Intervals 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 Intervals 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 Intervals can do together
From Buildkite to Intervals
When New build in Buildkite
then Add invoice in Intervals
From Intervals 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 Intervals
Triggers and actions 8 triggers · 50 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.
- New client
Polling trigger: fires when a new client is created in Intervals.
- New invoice
Polling trigger: fires when a new invoice is created in Intervals.
- New milestone
Polling trigger: fires when a new milestone is created in Intervals.
- New person
Polling trigger: fires when a new person is added in Intervals.
- New project
Polling trigger: fires when a new project is created in Intervals.
- New task
Polling trigger: fires when a new task is created in Intervals.
- Add client
Create a new client.
- Add expense
Create a new expense.
- Add invoice
Create a new invoice.
- Add milestone
Create a new milestone.
- Add person
Create a new person (team member).
- Add project
Create a new project.
- Add task
Create a new task.
- Add time entry
Log a new time entry against a task.
- Add timer
Start a new timer for a task.
- Delete client
Delete a client.
- Delete expense
Delete an expense.
- Delete invoice
Delete an invoice.
- Delete milestone
Delete a milestone.
- Delete person
Delete a person.
- Delete project
Delete a project.
- Delete task
Delete a task.
- Delete time entry
Delete a logged time entry.
- Delete timer
Delete a timer.
- Get client
Retrieve a single client by id.
- Get expense
Retrieve a single expense by id.
- Get invoice
Retrieve a single invoice by id.
- Get milestone
Retrieve a single milestone by id.
- Get person
Retrieve a single person by id.
- Get project
Retrieve a single project by id.
- Get task
Retrieve a single task by id.
- Get time entry
Retrieve a single logged time entry by id.
- Get timer
Retrieve a single timer by id.
- List milestones
Retrieve all milestones in the Intervals account.
- List tasks
Retrieve all tasks in the Intervals account.
- Update client
Update an existing client's details.
- Update expense
Update an existing expense.
- Update invoice
Update an existing invoice.
- Update milestone
Update an existing milestone.
- Update person
Update an existing person's details.
- Update project
Update an existing project's details.
- Update task
Update an existing task's details.
- Update time entry
Update an existing logged time entry.
- Update timer
Update a timer (e.g. stop or adjust it).
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 Intervals
QuickBooks Online to IntervalsQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
ActiveCampaign to IntervalsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Buildkite and Intervals, 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 Intervals when something happens in Buildkite?
Any of Intervals's 38 actions, including Update client, Update expense, Update invoice and Update milestone. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Intervals to Buildkite?
Yes. When something happens in Intervals, your agent can act in Buildkite too. This page covers both directions: Intervals's triggers and Buildkite's actions are listed here as well.
Do I have to build a connector for Buildkite or Intervals?
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.