# Bitbucket AI integration on Definable

> Bitbucket is a Git-based code hosting and collaboration platform supporting private and public repositories, enabling teams to manage and review code through pull requests and integrations

## What this connects

Bitbucket is a Git-based code hosting and collaboration platform supporting private and public repositories, enabling teams to manage and review code through pull requests and integrations

Vendor: https://bitbucket.org/

## Tools available

**107** tools available. First 12:

- `BITBUCKET_APPROVE_PULL_REQUEST` — Approve Pull Request — Tool to approve a pull request as the authenticated user. Use when you need to formally approve changes in a pull request review process.
- `BITBUCKET_BROWSE_REPOSITORY_PATH` — Browse repository path — Tool to retrieve content for a file path or browse directory contents at a specified revision in a Bitbucket repository. Use when you need flexible access to repository content - returns raw file data for files or paginated directory listings for directories.
- `BITBUCKET_CREATE_BRANCH` — Create a branch — Creates a new branch in a Bitbucket repository from a target commit hash; the branch name must be unique, adhere to Bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
- `BITBUCKET_CREATE_ISSUE` — Create an issue — Creates a new issue in a Bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component IDs exist.
- `BITBUCKET_CREATE_ISSUE_COMMENT` — Create an issue comment — Adds a new comment with markdown support to an existing Bitbucket issue.
- `BITBUCKET_CREATE_PULL_REQUEST` — Create a pull request — Creates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
- `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` — Create pull request comment — Creates a new comment on a Bitbucket pull request. Supports top-level comments, threaded replies, and inline code comments. Use when providing feedback on a PR, replying to existing comments, or commenting on specific code lines.
- `BITBUCKET_CREATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONS` — Create commit report annotations — Adds multiple annotations to a commit report in bulk. Use when you need to add code analysis findings (vulnerabilities, code smells, bugs) to a report attached to a specific commit.
- `BITBUCKET_CREATE_REPOSITORIES_COMMITS2` — List commits from revision (POST) — Tool to list commits from a revision using POST method. Identical to GET endpoint but allows sending include/exclude parameters in request body to avoid URL length limits. Use when include/exclude parameters are too long for query strings.
- `BITBUCKET_CREATE_REPOSITORY` — Create repository — Creates a new Bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project_key` is not provided.
- `BITBUCKET_CREATE_SNIPPET_COMMENT` — Create snippet comment — Posts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet.
- `BITBUCKET_CREATE_TEAMS_PIPELINES_CONFIG_VARIABLES` — Create team pipeline variable — Creates a team-level pipeline configuration variable in Bitbucket. Use when you need to add environment variables or configuration values that should be available to all pipelines within a team.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Bitbucket

Inside a Definable workflow, Bitbucket is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Bitbucket** — the Researcher (GPT-5.5) pulls context from Bitbucket (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Bitbucket** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Bitbucket (create record, post message, draft email).
- **Designer / Engineer → Distributor → Bitbucket** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Bitbucket (attach file, open PR comment, post status).

The Verifier checks every Bitbucket call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/bitbucket/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt