--- title: "Connect Buildkite and Google Calendar - APIANT.ai" description: "When \"New build\" fires in Buildkite, your agent runs \"Create Event\" in Google Calendar." canonical: "https://apiant.ai/connect/buildkite-to-google-calendar" --- # Connect Buildkite and Google Calendar When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Create Event** in [Google Calendar](https://apiant.ai/connections/google-calendar), or **Attendee Response Changed** in Google Calendar 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 Calendar **6** triggers Google Calendar **45** 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 Calendar 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 Calendar can do together ### From Buildkite to Google Calendar - When **New build** in Buildkite then **Create Event** in Google Calendar - When **Build finished** in Buildkite then **Update Event** in Google Calendar ### From Google Calendar to Buildkite - When **Attendee Response Changed** in Google Calendar then **Add annotation** in Buildkite - When **Event Created** in Google Calendar 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 Calendar ## Triggers and actions 8 triggers · 57 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 **Attendee Response Changed** Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status. - Trigger **Calendar Event Sync** Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook). - Trigger **Event Canceled or Deleted** Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp. - Trigger **Event Created** Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info. - Trigger **Event Starting Soon** Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available. - Trigger **Event Updated** Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values. - Action **Acl Delete** Deletes an access control rule from a Google Calendar. Use when you need to remove sharing permissions for a user, group, or domain. - Action **Acl Get** Retrieves a specific access control rule for a calendar. Use when you need to check permissions for a specific user, group, or domain. - Action **Acl Insert** Creates an access control rule for a calendar. Use when you need to grant sharing permissions to a user, group, or domain. - Action **Acl List** Retrieves the list of access control rules (ACLs) for a specified calendar, providing the necessary 'rule_id' values required for updating specific ACL rules. - Action **Acl Patch** Updates an existing access control rule for a calendar using patch semantics (partial update). This allows modifying specific fields without affecting other properties. IMPORTANT: The ACL rule must already exist on the calendar. This action cannot create new rules. If you receive a 404 Not Found error, the rule does not exist - use ACL insert to create it first, or use ACL list to verify available rules. Each patch request consumes three quota units. For domain-type ACL rules, if PATCH fails with 500 error, this action will automatically fallback to UPDATE method. - Action **Acl Update** Updates an access control rule for the specified calendar. - Action **Acl Watch** Tool to watch for changes to ACL resources. Use when you need to set up real-time notifications for access control list modifications on a calendar. - Action **Batch Events** Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results. Use this to materially reduce round-trips for bulk operations like migrations, cleanup, or large-scale updates. - Action **Calendar List Delete** Tool to remove a calendar from the user's calendar list. Use when you need to unsubscribe from or hide a calendar from the user's list. - Action **Calendar List Get** Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID. This action requires a calendarId parameter and returns details about that one calendar only. NOTE: This does NOT list all calendars. To list all calendars in the user's calendar list, use GOOGLECALENDAR_CALENDAR_LIST_LIST instead. - Action **Calendar List Insert** Inserts an existing calendar into the user's calendar list. - Action **Calendar List Patch** Updates an existing calendar on the user's calendar list using patch semantics. This method allows partial updates, modifying only the specified fields. - Action **Calendar List Update** Updates an existing entry on the user\'s calendar list. - Action **Calendar List Watch** Watch for changes to CalendarList resources using push notifications. Use this to receive real-time updates when calendar list entries are modified. - Action **Calendars Delete** Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars. - Action **Calendars Update** Updates metadata for a calendar. - Action **Channels Stop** Tool to stop watching resources through a notification channel. Use when you need to discontinue push notifications for a specific channel subscription. - Action **Create Calendar** Creates a new secondary Google Calendar with the specified title and optional settings. Use this action when you need to create a new calendar for organizing events separately from the primary calendar. The authenticated user becomes the owner of the newly created calendar. Optional parameters include description, location, and timezone. - Action **Create Event** Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true. - Action **Delete Event** Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found. - Action **Duplicate Calendar** Creates a new, empty google calendar with the specified title (summary). - Action **Events Get** Retrieves a SINGLE event by its unique event_id (REQUIRED). This action does NOT list or search events - it fetches ONE specific event when you already know its ID. If you want to list events within a time range, search for events, or filter by criteria like time_min/time_max, use GOOGLECALENDAR_EVENTS_LIST instead. - Action **Events Import** Tool to import an event as a private copy to a calendar. Use when you need to add an existing event to a calendar using its iCalUID. Only events with eventType='default' can be imported. - Action **Events Instances** Returns instances of the specified recurring event. - Action **Events List** Returns events on the specified calendar. - Action **Events List All Calendars** Return a unified event list across all calendars in the user's calendar list for a given time range. Use when you need a single view of all events across multiple calendars. An inverted or incorrect time range silently returns empty results rather than an error. An empty `items` list means no events matched the filters—adjust `time_min`, `time_max`, or `q` before concluding no events exist. - Action **Events Move** Moves an event to another calendar, i.e., changes an event's organizer. - Action **Events Watch** Watch for changes to events resources. - Action **Find Event** Finds events in a specified google calendar using text query, time ranges (event start/end, last modification), and event types; ensure `timemin` is not chronologically after `timemax` if both are provided. - Action **Find Free Slots** Finds free/busy time slots in google calendars for specified calendars within a defined time range (defaults to the current day utc if `time min`/`time max` are omitted), enhancing busy intervals with event details; `time min` must precede `time max` if both are provided. - Action **Free Busy Query** Returns free/busy information for a set of calendars. - Action **Get Calendar** Retrieves a specific google calendar, identified by `calendar id`, to which the authenticated user has access. - Action **Get Current Date Time** Gets the current date and time, allowing for a specific timezone offset. - Action **List Acl Rules** Retrieves the list of access control rules (acls) for a specified calendar, providing the necessary 'rule id' values required for updating specific acl rules. - Action **List Calendars** Retrieves calendars from the user's google calendar list, with options for pagination and filtering. - Action **Patch Calendar** Partially updates (patches) an existing google calendar, modifying only the fields provided; `summary` is mandatory and cannot be an empty string, and an empty string for `description` or `location` clears them. - Action **Patch Event** Updates specified fields of an existing event in a google calendar using patch semantics (array fields like `attendees` are fully replaced if provided); ensure the `calendar id` and `event id` are valid and the user has write access to the calendar. - Action **Quick Add** Parses natural language text to quickly create a basic google calendar event with its title, date, and time, suitable for simple scheduling; does not support direct attendee addition or recurring events, and `calendar id` must be valid if not 'primary'. - Action **Remove Attendee** Removes an attendee from a specified event in a google calendar; the calendar and event must exist. - Action **Settings Get** Tool to return a single user setting for the authenticated user. Use when you need to retrieve a specific calendar setting value. - Action **Settings List** Returns all user settings for the authenticated user. - Action **Settings Watch** Watch for changes to settings resources. - Action **Sync Events** Synchronizes google calendar events, performing a full sync if no `sync token` is provided or if a 410 gone error (due to an expired token) necessitates it, otherwise performs an incremental sync for events changed since the `sync token` was issued. - Action **Update Acl Rule** Updates an access control rule for the specified calendar. - Action **Update Event** Updates an existing event by `event id` in a google calendar; this is a full put replacement, so provide all desired fields as unspecified ones may be cleared or reset. ## 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 Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connections/google-calendar) 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 Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/buildkite-to-google-drive) ## More into Google Calendar - [ **Gmail to Google Calendar** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-google-calendar) - [ **Google Drive to Google Calendar** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-google-calendar) - [ **Mailchimp to Google Calendar** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-google-calendar) - [ **Pipedrive to Google Calendar** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-google-calendar) - [ **Airtable to Google Calendar** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-google-calendar) - [ **Trello to Google Calendar** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/trello-to-google-calendar) Questions ## Buildkite and Google Calendar, 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 Calendar when something happens in Buildkite? Any of Google Calendar's 45 actions, including Create Calendar, Create Event, Update Acl Rule and Update Event. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Google Calendar to Buildkite? Yes. When something happens in Google Calendar, your agent can act in Buildkite too. This page covers both directions: Google Calendar's triggers and Buildkite's actions are listed here as well. ### ### Do I have to build a connector for Buildkite or Google Calendar? 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 Calendar 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.