--- title: "Connect Buildkite and Google Tasks - APIANT.ai" description: "When \"New build\" fires in Buildkite, your agent runs \"Create Task List\" in Google Tasks." canonical: "https://apiant.ai/connect/buildkite-to-google-tasks" --- # Connect Buildkite and Google Tasks When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Create Task List** in [Google Tasks](https://apiant.ai/connections/google-tasks), or **New Task Created** in Google Tasks to **Add annotation** in Buildkite. Describe the whole flow and it is built, tested on every scenario and kept running. Buildkite **2** triggers Buildkite **12** actions Google Tasks **5** triggers Google Tasks **16** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Buildkite and Google Tasks to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Buildkite and Google Tasks can do together ### From Buildkite to Google Tasks - When **New build** in Buildkite then **Create Task List** in Google Tasks - When **Build finished** in Buildkite then **Update Task** in Google Tasks ### From Google Tasks to Buildkite - When **New Task Created** in Google Tasks then **Add annotation** in Buildkite - When **New Task List Created** in Google Tasks 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 Google Tasks ## Triggers and actions 7 triggers · 28 actions - Trigger **Build finished** Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed). - Trigger **New build** Triggers when a new build is scheduled in a Buildkite pipeline. - Action **Add annotation** Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context. - Action **Add build** Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build. - Action **Add pipeline** Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration. - Action **Cancel build** Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build. - Action **Delete pipeline** Permanently deletes a pipeline from your Buildkite organization. - Action **Get build** Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details. - Action **Get pipeline** Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts. - Action **List agents** Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue. - Action **List builds** Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range. - Action **List pipelines** Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL. - Action **Rebuild build** Starts a new build that re-runs an existing build of a pipeline, and returns the new build. - Action **Update pipeline** Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters. - Trigger **New Task Created** Triggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks. - Trigger **New Task List Created** Triggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected. - Trigger **Task Details Changed** Triggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified. - Trigger **Task List Changed** Triggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected. - Trigger **Task Updated** Triggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified. - Action **Batch Execute** Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Use this to reduce LLM tool invocations when performing bulk operations like updating many tasks, moving tasks, or deleting multiple items. Note: Each sub-request still counts toward API quota; batching primarily reduces HTTP overhead and tool call count. - Action **Clear Tasks** Permanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent. - Action **Create Task List** Creates a new task list with the specified title. - Action **Delete Task** Deletes a specified task from a given task list in google tasks. - Action **Delete Task List** Permanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible. - Action **Get Task** Use to retrieve a specific google task if its `task id` and parent `tasklist id` are known. - Action **Get Task List** Retrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user. - Action **Insert Task** Creates a new task in a given `tasklist id`, optionally as a subtask of an existing `task parent` or positioned after an existing `task previous` sibling, where both `task parent` and `task previous` must belong to the same `tasklist id` if specified. - Action **List Task Lists** Fetches the authenticated user's task lists from google tasks; results may be paginated. - Action **List Tasks** Retrieves tasks from a google tasks list; all date/time strings must be rfc3339 utc, and `showcompleted` must be true if `completedmin` or `completedmax` are specified. - Action **Move Task** Moves the specified task to another position in the destination task list. - Action **Patch Task** Partially updates an existing task (identified by `task id`) within a specific google task list (identified by `tasklist id`), modifying only the provided attributes from `taskinput` (e.g., `title`, `notes`, `due` date, `status`) and requiring both the task and list to exist. - Action **Patch Task List** Updates the title of an existing google tasks task list. - Action **Update Task** Updates the specified task. - Action **Update Task Full** Tool to fully replace an existing Google Task using PUT method. Use when you need to update the entire task resource, not just specific fields. This method requires all required fields (id, title) and replaces the complete task, unlike PATCH which supports partial updates. - Action **Update Task List** Updates the authenticated user's specified task list. ## Each app on its own - [ **Buildkite** Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own...](https://apiant.ai/connections/buildkite) - [ **Google Tasks** Google Tasks provides a simple to-do list and task management system integrated into Gmail and Google...](https://apiant.ai/connections/google-tasks) Reviews ## What our customers say ## More from Buildkite - [ **Buildkite to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/buildkite-to-hubspot) - [ **Buildkite to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/buildkite-to-salesforce) - [ **Buildkite to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/buildkite-to-slack) - [ **Buildkite to Google Sheets** Google Sheets](https://apiant.ai/connect/buildkite-to-google-sheets) - [ **Buildkite to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/buildkite-to-gmail) - [ **Buildkite to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/buildkite-to-google-calendar) ## More into Google Tasks - [ **Every.org to Google Tasks** Every.org is a nonprofit that simplifies modern fundraising for charitable organizations of all sizes.](https://apiant.ai/connect/every-org-to-google-tasks) - [ **Slack to Google Tasks** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-google-tasks) - [ **Google Sheets to Google Tasks** Google Sheets](https://apiant.ai/connect/google-sheets-to-google-tasks) - [ **Gmail to Google Tasks** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-google-tasks) - [ **Google Drive to Google Tasks** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-google-tasks) - [ **Pipedrive to Google Tasks** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-google-tasks) Questions ## Buildkite and Google Tasks, 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 Google Tasks when something happens in Buildkite? Any of Google Tasks's 16 actions, including Create Task List, Update Task, Update Task Full and Update Task List. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Google Tasks to Buildkite? Yes. When something happens in Google Tasks, your agent can act in Buildkite too. This page covers both directions: Google Tasks's triggers and Buildkite's actions are listed here as well. ### ### Do I have to build a connector for Buildkite or Google Tasks? 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 Google Tasks 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.