Connect Bitbucket to Definable AI

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

About Bitbucket

Bitbucket is a productivity tool. Connect it to Definable AI with one-click OAuth2 — no API keys or custom code required.

What you can automate with Bitbucket

Use Definable AI's agent platform to trigger workflows from Bitbucket, process results with 50+ AI models, and sync data across 900+ connected apps.

Tools & Actions (111 available)

  • 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.
  • 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.
  • Check if user voted for issue: Tool to check whether the authenticated user has voted for a specific issue in a Bitbucket repository. Use when you need to verify if the current user has already voted on an issue before attempting to vote or unvote.
  • 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.
  • 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.
  • 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.
  • Create an issue comment: Adds a new comment with markdown support to an existing Bitbucket issue.
  • 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.
  • 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.
  • 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.
  • Create snippet comment: Posts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet.
  • 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.
  • Create user pipeline variable: Creates a user-level pipeline variable for Bitbucket pipelines. Use when you need to create account-level configuration variables that can be used across all repositories owned by the user.
  • Delete commit comment: Permanently deletes a specific comment on a commit. Use when removing outdated, incorrect, or unwanted feedback on a commit.
  • Delete commit report annotation: Deletes a single annotation matching the provided ID from a commit report. Use when you need to remove a specific annotation from a code analysis report.
  • Delete issue: Permanently deletes a specific issue, identified by its `issue_id`, from the repository specified by `repo_slug` within the given `workspace`.
  • Delete repository: Permanently deletes a specified Bitbucket repository; this action is irreversible and does not affect forks.
  • Delete snippet watch: Stops watching a specific snippet. Use when you want to unsubscribe from notifications for a snippet.
  • Delete user pipeline variable: Permanently deletes a user-level pipeline configuration variable identified by its UUID. Use this to remove pipeline variables that are no longer needed at the account level.
  • Get Commit Build Status: Get a specific build status for a commit in Bitbucket. Use when you need to check the status of a particular build/CI run for a commit.
  • Get Commit Changes: Tool to retrieve a page of changes made in a specified commit, showing all changed files with their change statistics (lines added/removed, status). Use when you need to enumerate files modified in a specific commit or commit range.
  • Get Commit Diff: Tool to retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket repository. Use when you need to see the actual code changes in a commit or between two commits. Supports filtering by file path and various diff options.
  • Get Commit Reports: Tool to get reports linked to a specific commit. Use when you need to retrieve analysis results, test reports, security scans, or code coverage data associated with a commit.
  • Get Merge Base: Tool to find the best common ancestor (merge base) between two commits in a Bitbucket repository. Use when you need to determine the point where two branches diverged or find the common parent commit.
  • Get OpenID configuration for OIDC in Pipelines: Retrieves the OpenID Connect discovery configuration for Bitbucket Pipelines OIDC. Use when integrating Bitbucket Pipelines with resource servers (AWS, GCP, Vault) using OpenID Connect authentication. Returns issuer URL, JWKS URI, and supported capabilities.
  • Get Pull Request: Get a single pull request by ID with complete details.
  • Get Pull Request Commits: Tool to retrieve commits for a specified pull request. Use when reviewing the commit history of a PR or analyzing changes included in a pull request.
  • Get Pull Request Diff: Tool to fetch the unified diff for a Bitbucket pull request (follows 302 redirect to repository diff). Use when reviewing code changes in a PR. Supports optional truncation for large diffs via max_chars parameter.
  • Get Pull Request Diffstat: Tool to get the diffstat for a Bitbucket pull request, showing all changed files with their change statistics (lines added/removed, status). Use when you need to enumerate files modified in a PR.
  • Get Repositories Diff: Tool to fetch the raw git-style diff between commits in a Bitbucket repository. Use when comparing code changes between commits or branches. Supports filtering by path and various diff options.
  • Get Repositories Merge Base: Get the merge base (best common ancestor) between two commits in a Bitbucket repository. Use when you need to find the common ancestor commit between two branches or commits for comparison or merge operations.
  • Get Repository Branching Model: Return the branching model as applied to the repository. Use when you need to understand the repository's branch workflow configuration, including development/production branches and branch type prefixes.
  • Get Repository Commit: Tool to retrieve detailed information about a specific commit in a Bitbucket repository. Use when you need to get complete commit details including author, message, date, parents, and related links.
  • Get Repository Environment: Retrieve detailed information about a specific deployment environment in a Bitbucket repository. Use when you need to get environment configuration, deployment settings, or check environment properties like locks and restrictions.
  • Get Repository Patch: Tool to retrieve the git patch content for a Bitbucket repository at a specified revision or commit range. Use when you need to review code changes, generate diffs, or analyze modifications between commits. Returns raw patch in unified diff format.
  • Get SSH keys for user: Retrieves a paginated list of SSH keys for a specified Bitbucket user. Use when you need to view or audit SSH keys configured for a user account.
  • Get Workspace Pull Requests by User: Tool to get all workspace pull requests authored by a specified user. Use when you need to retrieve pull requests created by a specific user across all repositories in a workspace.
  • Get branch: Retrieves detailed information about a specific branch in a Bitbucket repository. Use when you need to get branch metadata, the commit it points to, or verify a branch exists.
  • Get commit comment: Retrieves a specific comment from a commit by its ID. Use when you need to fetch details of a particular commit comment including content, author, timestamps, and inline location.
  • Get commit comments: Retrieves all comments on a specific commit in a Bitbucket repository. Returns both global and inline code comments. Use when you need to view feedback, discussions, or notes left on a specific commit.
  • Get commit report: Returns a single report matching the provided ID from a commit. Use when you need to retrieve details of a specific analysis report (e.g., security scan, code coverage, test results, or bug report) for a commit.
  • Get commit report annotation: Returns a single annotation matching the provided ID from a commit report. Use when you need to retrieve details of a specific code analysis finding (e.g., vulnerability, code smell, or bug) identified in a commit.
  • Get commit statuses: Returns all build statuses (e.g., CI/CD pipeline results) for a specific commit. Use when you need to check build status, verify test results, or monitor deployment pipelines for a particular commit.
  • Get current user: Retrieves the profile information (UUID, display name, links, creation date) for the currently authenticated Bitbucket user.
  • Get current user (v2): Tool to retrieve complete profile information for the currently authenticated Bitbucket user. Use when you need comprehensive user details including account_id, username, nickname, and other profile fields.
  • Get deployment environment variables: Retrieves deployment environment level variables for a specific Bitbucket repository environment. Use when you need to view or audit environment-specific configuration variables for deployments.
  • Get effective branching model: Retrieves the effective branching model for a Bitbucket repository, showing which branching model is currently applied (including any inheritance from project-level settings). Use when you need to understand the repository's branch workflow configuration, including development and production branches and branch type prefixes.
  • Get file commit history: Returns a paginated list of commits that modified the specified file. Use when you need to track file changes over time, find who modified a file, or determine when a file was created or last changed.
  • Get file from repository: Retrieves a specific file's content from a Bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.
  • Get hook events: Retrieves a paginated list of all valid webhook events for a specified entity type (repository or workspace). Use when you need to discover available webhook event types for subscription or webhook configuration.
  • Get pipeline steps: Retrieves all steps for a given pipeline. Use when you need to inspect the individual steps of a pipeline execution, including their state, duration, and commands.
  • Get project repositories: Retrieves repositories from a project in a Bitbucket workspace. Use when you need to list all repositories belonging to a specific project key within a workspace.
  • Get pull request comment: Tool to retrieve a specific comment from a pull request by its ID. Use when you need to fetch details of a particular pull request comment including content, author, timestamps, and inline location.
  • Get pull request comments: Retrieves a paginated list of comments on a specific pull request in a Bitbucket repository. Returns global, inline, and threaded comments. Use when you need to view feedback, discussions, or reviews left on a pull request.
  • Get pull request statuses: Returns all build statuses (e.g., CI/CD pipeline results) for a specific pull request. Use when you need to check build status, verify test results, or monitor deployment pipelines for a pull request.
  • Get pull requests activity log: Get paginated activity log for all pull requests in a repository. Returns comments, updates, approvals, and request changes. Use when you need to track pull request activity history.
  • Get raw file content: Tool to retrieve the raw content of a file from a Bitbucket repository at a specified commit, branch, or tag. Use when you need to read file contents from a specific revision.
  • Get repositories src: Lists the contents of the root directory on the repository's main branch without needing to specify a commit or branch. This endpoint redirects to the main branch automatically.
  • Get repository: Retrieves detailed information about a specific repository in a Bitbucket workspace. Use when you need to get repository metadata, settings, or details.
  • Get repository SSH known hosts: Retrieves repository-level SSH known hosts configured for Bitbucket Pipelines. Use when you need to list or verify SSH known hosts that Pipelines can connect to during builds.
  • Get repository commits: Lists all commits in a Bitbucket repository with optional filtering by branch, revision range, or file path. Use when you need to retrieve commit history, analyze changes, or find commits affecting specific files.
  • Get repository pipeline runners: Retrieves the list of self-hosted runners configured for a repository's pipelines. Use when you need to view available runners for pipeline execution.
  • Get repository pipeline schedules: Retrieves configured pipeline schedules for a Bitbucket repository. Use when you need to view scheduled pipeline runs and their cron patterns.
  • Get repository pipeline variables: Retrieves repository-level pipeline variables for a specific Bitbucket repository. Use when you need to view or audit pipeline configuration variables that are scoped to a repository.
  • Get repository pipelines caches: Retrieves the repository pipelines caches. Use when you need to list all caches configured for Bitbucket Pipelines in a specific repository.
  • Get repository refs: Returns the branches and tags in the repository. Use when you need to list all refs (both branches and tags) in a single API call with optional filtering by type, name pattern, or commit hash.
  • Get repository source content: Tool to retrieve the contents of a single file or list directory contents from a Bitbucket repository at a specified commit, branch, or tag. Use when you need to read file contents or browse directory structure from a specific revision.
  • Get repository watchers: Retrieves a paginated list of all the watchers on the specified repository. Use when you need to see who is watching a particular repository.
  • Get snippet: Retrieves a specific Bitbucket snippet by its encoded ID from an existing workspace, returning its metadata and file structure.
  • Get snippet watch status: Checks if the current user is watching a specific snippet. Use when you need to verify watch status for a snippet.
  • Get specific pipeline: Retrieve a specified pipeline from a Bitbucket repository. Use when you need to get detailed information about a specific pipeline execution including its status, build number, and results.
  • Get tag: Retrieves detailed information about a specific tag in a Bitbucket repository. Use when you need to get tag metadata, target commit details, or verify a tag exists.
  • Get user: Retrieves public profile information for a specific Bitbucket user by username or UUID. Use when you need to get user details like display name, avatar, creation date, and links to related resources.
  • Get user email details: Retrieves details about a specific email address for the authenticated user. Use when you need to check if an email is primary, confirmed, or verify email ownership.
  • Get user emails: Returns all the authenticated user's email addresses, both confirmed and unconfirmed. Use when you need to retrieve all email addresses associated with the current user's account.
  • Get user permissions for repositories: Returns an object for each repository the caller has explicit access to, including their permission level. Use when you need to discover which repositories the authenticated user can access and their specific permissions.
  • Get user permissions for workspaces: Retrieves workspace memberships and permission levels for the authenticated user. Returns an object for each workspace the caller is a member of, along with their effective role (highest privilege level). Use when you need to determine which workspaces a user can access and their permission level in each.
  • Get user workspaces: Tool to retrieve all workspaces accessible to the authenticated user. Use when you need to list workspaces the current user can access, optionally filtered by workspace slug or permission level.
  • Get user's SSH keys: Retrieves a paginated list of SSH public keys for a specified Bitbucket user. Use when you need to list or verify SSH keys associated with a user account.
  • Get workspace: Retrieves detailed information about a specific Bitbucket workspace. Use when you need to get workspace metadata, settings, or details.
  • List all public repositories: Retrieves a paginated list of all public repositories on Bitbucket. Use when you need to discover or search across public repositories, optionally filtered by role, query string, creation date, or sorted by various fields.
  • List branches: Lists branches in a Bitbucket repository with optional server-side filtering by name pattern (BBQL) and sorting. Use when you need to discover available branches, search for specific branch patterns, or navigate repository branch structure.
  • List commits: Tool to retrieve a page of commits from a Bitbucket repository. Returns commits in reverse chronological order (newest first), similar to git log. Use when you need to browse commit history, filter commits by branch/tag, or restrict to commits affecting a specific path.
  • List commits from revision: Tool to list commits starting from a specific revision in a Bitbucket repository. Commits are paginated and returned in reverse chronological order. Use when you need to retrieve commit history from a specific commit, branch, or tag.
  • 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.
  • List commits on master: Lists commits on the master branch of a Bitbucket repository. Use when you need to retrieve the commit history for the master branch, including commit messages, authors, dates, and parent relationships.
  • List deployments: Lists deployments for a specified Bitbucket repository. Use when you need to view deployment history and status across environments.
  • List issues in a repository: Lists issues in a Bitbucket repository with optional filtering by state, priority, kind, or assignee. Use when you need to discover issue IDs or get an overview of repository issues.
  • List pipelines: Tool to find pipelines in a Bitbucket repository. Returns pipeline metadata including state, trigger, and duration. Use when you need to browse pipeline history or check pipeline status.
  • List pull request tasks: Lists all tasks associated with a pull request in a Bitbucket repository. Use when you need to view or track tasks on a PR.
  • List pull requests: Lists pull requests in a specified, accessible Bitbucket repository, optionally filtering by state (OPEN, MERGED, DECLINED).
  • List repositories in workspace: Lists repositories in a specified Bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results.
  • List repository environments: List all deployment environments configured for a Bitbucket repository. Use when you need to view available environments for deployments, check environment configurations, or select an environment for deployment operations.
  • List repository paths: Lists file and directory entries under a repository path at a given revision, with optional breadth-first recursion via max_depth for repository traversal and scanning. Fails if the path points to a file rather than a directory.
  • List snippets: Returns all snippets accessible to the authenticated user. Use when you need to discover or list snippets, optionally filtered by role (owner, contributor, or member).
  • List tags: Lists tags in a Bitbucket repository with optional server-side filtering by name pattern or commit hash (BBQL) and sorting. Use when you need to discover available tags, search for specific tag patterns, or find tags pointing to specific commits.
  • List versions: Lists versions (milestones) in a Bitbucket repository's issue tracker. Use when you need to discover available versions for associating with issues, or to retrieve version IDs for use with create_issue.
  • List workspace members: Lists all members of a specified Bitbucket workspace; the workspace must exist.
  • List workspace projects: Lists projects in a specified Bitbucket workspace. Use when you need to retrieve all projects belonging to a workspace.
  • List workspaces: Lists Bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted.
  • Request Pull Request Changes: Tool to request changes on a pull request as the authenticated user. Use when you need to formally request changes in a pull request review process, indicating the PR needs modifications before approval.
  • Search code in team repositories: Search for code in repositories of a specified team. Matches can occur in file content or paths. Note: Teams endpoints were deprecated in Oct 2020; use workspace search endpoints for new integrations.
  • Search code in user repositories: Tool to search for code in the repositories of a specified user. Use when you need to find specific code patterns, functions, or text across all repositories owned by a user.
  • Search code in workspace: Tool to search for code in the repositories of the specified workspace. Use when you need to find specific code patterns, function definitions, or text across all repositories in a workspace.
  • Update an issue: Updates an existing issue in a Bitbucket repository by modifying specified attributes; requires `workspace`, `repo_slug`, `issue_id`, and at least one attribute to update.
  • Update commit comment: Updates the contents of a comment on a commit. Use when you need to modify an existing comment's text on a commit.
  • Update commit insight report: Create or update an insight report for a commit. Creates a new report if it doesn't exist, or replaces the existing one if a report already exists for the given repository, commit, and report key. Note: replacing an existing report will be rejected if the authenticated user was not the creator of the specified report.
  • Update commit report: Creates or updates a report for a specific commit. Use when you need to attach analysis results (security scans, code coverage, test results, or bug reports) to a commit in Bitbucket.
  • Update commit report annotation: Creates or updates an individual annotation for a commit report. Use when you need to add or modify code analysis findings (vulnerabilities, code smells, or bugs) identified in a commit.
  • Update team pipeline variable: Updates a team-level pipeline configuration variable in Bitbucket. Use when you need to modify existing environment variables or configuration values that are available to all pipelines within a team.
  • Update user pipeline variable: Updates a user-level pipeline variable for Bitbucket pipelines. Use when you need to modify account-level configuration variables such as changing the value, key name, or security status.

How to connect Bitbucket

  1. Sign in to Definable AI and go to Apps
  2. Search for Bitbucket and click Connect
  3. Authorize via OAuth2 — takes under 30 seconds
  4. Use Bitbucket actions in your AI agents and workflows