--- title: "Connect Bitbucket to Google Cloud Scheduler - APIANT.ai" description: "When \"New pull request\" fires in Bitbucket, your agent runs \"Create HTTP Job\" in Google Cloud Scheduler." canonical: "https://apiant.ai/connect/bitbucket-to-google-cloud-scheduler" --- # Connect Bitbucket to Google Cloud Scheduler When **New pull request** fires in [Bitbucket](https://apiant.ai/connections/bitbucket), your agent runs **Create HTTP Job** in [Google Cloud Scheduler](https://apiant.ai/connections/google-cloud-scheduler). Describe the whole flow and it is built, tested on every scenario and kept running. Bitbucket **1** trigger Bitbucket **9** actions Google Cloud Scheduler **8** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Bitbucket and Google Cloud Scheduler 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 Bitbucket can start in Google Cloud Scheduler - When **New pull request** in Bitbucket then **Create HTTP Job** in Google Cloud Scheduler - When **New pull request** in Bitbucket then **Update Job** in Google Cloud Scheduler 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 Bitbucket and Google Cloud Scheduler ## Triggers and actions 1 trigger · 17 actions - Trigger **New pull request** - Action **Add branch** /2.0/repositories/{workspace}/{repo_slug}/refs/branches - Action **Add pull request** /2.0/repositories/{workspace}/{repo_slug}/pullrequests - Action **Add pull request comment** /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}/comments - Action **Add repository** /2.0/repositories/{workspace}/{repo_slug} - Action **Get pull request** /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id} - Action **List branches** /2.0/repositories/{workspace}/{repo_slug}/refs/branches - Action **List pull requests** /2.0/repositories/{workspace}/{repo_slug}/pullrequests - Action **List repositories** /2.0/repositories/{workspace} - Action **Update pull request** /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id} - Action **Create HTTP Job** Creates a Cloud Scheduler job that calls an HTTP URL on a cron schedule. - Action **Delete Job** Permanently deletes a Cloud Scheduler job. - Action **Get Job** Returns a Cloud Scheduler job's schedule, target and current state. - Action **List Jobs** Returns the Cloud Scheduler jobs in a project location. - Action **Pause Job** Pauses a Cloud Scheduler job so it stops running on its schedule until resumed. - Action **Resume Job** Resumes a paused Cloud Scheduler job so it runs on its schedule again. - Action **Run Job Now** Runs a Cloud Scheduler job immediately. The job must be enabled; a paused job has to be resumed first. - Action **Update Job** Changes a Cloud Scheduler HTTP job's schedule, time zone, URL, method or description. Fields left blank are not changed. ## Each app on its own - [ **Bitbucket** Git repository hosting platform with pull request code review and built-in CI/CD pipelines, integrated with...](https://apiant.ai/connections/bitbucket) - [ **Google Cloud Scheduler** Managed cron service for scheduling HTTP, Pub/Sub and App Engine jobs on Google Cloud.](https://apiant.ai/connections/google-cloud-scheduler) Reviews ## What our customers say ## More from Bitbucket - [ **Bitbucket to Vercel** Vercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.](https://apiant.ai/connect/bitbucket-to-vercel) - [ **Bitbucket to change.photos** change.photos is an API for streamlined image transformations - resize, compress, sharpen, blur, and rotate...](https://apiant.ai/connect/bitbucket-to-change-photos) - [ **Bitbucket to Football Charts** Tables, results, model probabilities and Monte Carlo season projections for 93 leagues](https://apiant.ai/connect/bitbucket-to-football-charts) - [ **Bitbucket to Fruityvice** Fruityvice is a reference service for fruit data including botanical classification and nutrition.](https://apiant.ai/connect/bitbucket-to-fruityvice) - [ **Bitbucket to Geneea Natural Language Processing**](https://apiant.ai/connect/bitbucket-to-geneea-natural-language-processing) - [ **Bitbucket to Tempo** Project, portfolio, and resource management add-on for Jira, including time tracking and budget planning.](https://apiant.ai/connect/bitbucket-to-tempo) ## More into Google Cloud Scheduler - [ **HubSpot to Google Cloud Scheduler** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-google-cloud-scheduler) - [ **Salesforce to Google Cloud Scheduler** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-google-cloud-scheduler) - [ **Slack to Google Cloud Scheduler** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-google-cloud-scheduler) - [ **Google Sheets to Google Cloud Scheduler** Google Sheets](https://apiant.ai/connect/google-sheets-to-google-cloud-scheduler) - [ **Gmail to Google Cloud Scheduler** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-google-cloud-scheduler) - [ **Google Calendar to Google Cloud Scheduler** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-google-cloud-scheduler) Questions ## Bitbucket and Google Cloud Scheduler, answered ### ### What can start an automation from Bitbucket? Any of Bitbucket's 1 trigger in the catalog, including New pull request. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Google Cloud Scheduler when something happens in Bitbucket? Any of Google Cloud Scheduler's 8 actions, including Create HTTP Job, Update Job, Get Job and List Jobs. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Google Cloud Scheduler to Bitbucket? Google Cloud Scheduler has no triggers in the catalog today, so automations start in Bitbucket. If you need the other direction, ask: your agent reads Google Cloud Scheduler's API documentation and adds it. ### ### Do I have to build a connector for Bitbucket or Google Cloud Scheduler? 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 Bitbucket and Google Cloud Scheduler 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.