Skip to content
ClickRuntime

Automate Bitbucket

Keep pull requests moving and broken builds visible across your Bitbucket workspace. Failed pipelines, newly opened PRs, reviews that have sat for days and weekly merge counts reach you by email or chat instead of waiting in a repo tab. Tell your AI assistant which repos and branches matter, look over the plan it proposes, and the job carries on from there.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: whenever a build on our acme/web-app Bitbucket repo fails, email me the commit message, the author and a link to the pull request it belongs to.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Bitbucket

Know within minutes when a build breaks, see every new pull request with its reviewers, and catch reviews that have been waiting too long. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get an email when a Bitbucket build fails

As soon as a pipeline or build fails, you get the commit and the pull request it belongs to.

See how it works
Every 5 minutes

Post new Bitbucket pull requests to Slack

Each newly opened pull request shows up in your team channel with its author and reviewers.

See how it works
On a schedule

Get a morning list of pull requests waiting too long

Every weekday you see which pull requests have been open for more than three days, so reviews do not stall.

See how it works
On a schedule

Get a weekly pull request report per repo

Each Monday you see how many pull requests were opened, merged and declined in every repo last week, and by whom.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Bitbucket, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Bitbucket automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Bitbucket should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, check Bitbucket for pull requests waiting on review for more than 2 days and send me the list per repository.

When a pull request is merged in Bitbucket, post the title and author to our #deploys Slack channel.

When a Bitbucket pull request mentions a Jira key, move that Jira issue to In Review, comment the PR link, and notify the reviewer in Slack.

Beyond chat

Have Bitbucket work when you're not in the chat

Connecting Bitbucket to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Bitbucket

Bitbucket connects with an Atlassian API token that you create under your own Atlassian account. You pick the Bitbucket scopes, so it can only read or change what you allowed.

Bitbucket

Developer / Source control

  1. In your Atlassian account, open Security, then Create and manage API tokens, and choose Create API token with scopes.
  2. Give the token a name and an expiry date, and choose Bitbucket as the app.
  3. Tick the scopes your automation needs, for example read:repository:bitbucket, read:pullrequest:bitbucket and read:workspace:bitbucket, then copy the token right away.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token together with the email address of your Atlassian account.

Good to know

Bitbucket limits that affect automations

  • An Atlassian API token lasts at most 365 days, so plan to replace it before it expires or your Bitbucket automations stop.
  • The token is shown only once when you create it. If you lose it, create a new one.
  • A call that needs a scope the token lacks fails with a 403 error, so choose scopes to match what each automation reads.
  • App passwords are being phased out by Atlassian. Use a scoped API token instead.

FAQ

Questions about automating Bitbucket

Which Bitbucket data can ClickRuntime read?
Whatever your token's scopes cover. With the repository, pull request and workspace read scopes it can list repos, open and merged PRs, their authors and reviewers, and commit build status.
Can I still use a Bitbucket app password?
Atlassian is retiring app passwords, so ClickRuntime uses API tokens with scopes. They are created in your Atlassian account settings and sent with your account email.
Does a failed pipeline alert arrive instantly?
It can. A Bitbucket webhook for commit status updates sends the failure the moment it is reported. Adding that webhook needs admin rights on the repo, either through the `admin:webhook` scope or by setting it up yourself in the repo settings.
How are new pull requests picked up without a webhook?
The automation checks your open pull requests every few minutes, posts the ones it has not seen yet and remembers their IDs so nothing is announced twice.
Is AI involved in these Bitbucket automations?
Not for the ones listed here; they filter and count PRs and builds directly. If you later want summaries of PR descriptions, the AI included in every ClickRuntime plan handles it without a key of your own.
Is this a Bitbucket connector for ChatGPT or Claude?
Not for chatting with Bitbucket data. A chat connector lets your assistant read and change Bitbucket while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Bitbucket event.

Related pages

Keep exploring

Tell your assistant what Bitbucket should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude