Skip to main content
Bitbucket logo
  • Category: developer tools
  • Auth: OAUTH2
  • Composio-managed OAuth available? Yes
  • Tools: 118
  • Triggers: 0
  • Slug: BITBUCKET
  • Version: 20261101_00

Tools

Slug: BITBUCKET_APPROVE_PULL_REQUESTTool to approve a pull request as the authenticated user. Use when you need to formally approve changes in a pull request review process.

Input Parameters

string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to approve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_BROWSE_REPOSITORY_PATHRetrieves file content or browses directory contents at a specified revision in a Bitbucket repository. File content is returned as text or base64-encoded binary data; directory listings are paginated, and metadata can also be requested.

Input Parameters

string
Filter query string using Bitbucket’s REST API filtering syntax to narrow results. Only applicable when browsing directories.
integer
Page number for paginated results (starts from 1). Only applicable when browsing directories.
string
File or directory path within the repository to browse. Use empty string for root directory.
string
Field name for sorting results. Prefix with ’-’ for descending order. Only applicable when browsing directories.
string
Commit hash, branch name, or tag to browse from. Defaults to ‘master’ if not specified.
string
Response format. Use ‘meta’ to return metadata as JSON instead of raw file contents when browsing a file.
integer
Number of entries per page (1-100). Only applicable when browsing directories. Controls pagination size.
integer
Maximum depth for breadth-first recursive directory traversal. Only applicable when path is a directory. Large values may cause timeouts.
string
required
Repository slug or UUID (typically URL-formatted name).
string
required
Workspace ID or UUID (often username or team name) containing the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_BRANCHCreates 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.

Input Parameters

string
required
The name for the new branch (e.g., ‘feature/new-login’, ‘bugfix/issue-123’). Important: Do not include the ‘refs/heads/’ prefix.
string
required
The slug or UUID of the repository where the branch will be created. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or UUID that owns the repository. This can typically be found in the URL of your Bitbucket workspace.
string
required
The full commit hash (SHA1) from which the new branch will be created. This commit must exist in the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_ISSUECreates 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.

Input Parameters

string
Type of the issue (e.g., ‘bug’, ‘enhancement’, ‘proposal’, ‘task’).
string
required
Title for the new issue.
string
Due date for the issue in ISO 8601 format (e.g., ‘YYYY-MM-DDTHH:mm:ssZ’).
string
required
Detailed description for the new issue.
string
Bitbucket username of the assignee. The assignee must have repository access.
string
Priority level of the issue (e.g., ‘trivial’, ‘minor’, ‘major’, ‘critical’, ‘blocker’).
string
required
The slug of the Bitbucket repository.
string
required
The ID or slug of the Bitbucket workspace.
integer
Numeric ID of an existing version to associate with this issue.
integer
Numeric ID of an existing component to associate with this issue.
integer
Numeric ID of an existing milestone to associate with this issue.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_ISSUE_COMMENTAdds a new comment with markdown support to an existing Bitbucket issue.

Input Parameters

string
required
The raw text content for the comment. This content supports markdown formatting, which Bitbucket will then render.
string
required
The unique identifier of the issue on which the comment will be posted.
string
required
The slug (URL-friendly version) of the repository name.
string
required
The ID or slug of the workspace or user that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_PULL_REQUESTCreates a new pull request in a specified Bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.

Input Parameters

string
required
Concise title summarizing the changes for the pull request.
string
required
Slug (URL-friendly name) of the repository for the pull request.
array
List of Bitbucket user UUIDs to be added as reviewers. Malformed or non-existent UUIDs trigger validation errors.
string
required
Workspace ID (UUID or slug) of the repository owner.
string
Detailed Markdown description of the pull request, outlining changes and purpose.
string
required
Name of the source branch with changes to be merged.
string
Name of the destination branch for merging; defaults to repository’s main branch if unspecified.
boolean
If true, automatically closes the source branch upon pull request merge.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_PULL_REQUEST_COMMENTCreates 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.

Input Parameters

object
Location details for inline code comments.
string
required
The slug (URL-friendly version) of the repository name.
string
required
The ID or slug of the workspace that owns the repository.
string
required
The raw text content for the comment. Supports markdown formatting which Bitbucket will render.
integer
required
The unique identifier of the pull request to comment on.
integer
ID of an existing comment to reply to, creating a threaded comment. If omitted, creates a top-level comment.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONSAdds 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.

Input Parameters

string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
The unique identifier of the report to which annotations will be added.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.
array
required
Array of annotation objects to be added to the report. Each annotation must have path, line, summary, and severity.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_REPOSITORIES_COMMITS2Tool 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.

Input Parameters

integer
Page number for paginated results (starts from 1).
string
Optional file path to filter commits. Only commits that modified this file or directory will be returned.
string
Optional commit hash or branch to exclude from the results. Can be used to create a range with the ‘include’ parameter. Use POST method when this value is very long.
string
Optional commit hash or branch to include in the results. Can be used to create a range with the ‘exclude’ parameter. Use POST method when this value is very long.
integer
Number of commits per page (1-100). Bitbucket default is typically 30 if not specified.
string
required
The commit hash, branch name, tag, or other revision identifier to start listing commits from. Commits are returned in reverse chronological order starting from this revision.
string
required
The slug of the repository. This is the repository’s name, usually in lowercase and with hyphens instead of spaces.
string
required
The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_REPOSITORYCreates a new Bitbucket ‘git’ repository in a specified workspace, defaulting to the workspace’s oldest project if project_key is not provided.

Input Parameters

boolean
Enable the wiki (True), or disable it (False).
string
Primary programming language (e.g., ‘python’, ‘java’) for categorization.
string
required
URL-friendly slug for the new repository.
string
required
Workspace identifier. Can be a slug (e.g., ‘my-workspace’) or UUID with curly braces (e.g., ‘{uuid}’). Bare UUIDs without braces are automatically normalized to the required format.
boolean
Enable the issue tracker (True), or disable it (False).
boolean
Repository visibility: True for private, False for public.
string
Description for the new repository.
string ("allow_forks" | "no_public_forks" | "no_forks")
Forking policy for the repository, determining who can create forks.
string
Key of the Bitbucket project for the repository; if omitted, it’s placed in the workspace’s oldest project.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_SNIPPET_COMMENTPosts a new top-level comment or a threaded reply to an existing comment on a specified Bitbucket snippet.

Input Parameters

string
required
Raw text content of the comment; Bitbucket will render any included markup (like Markdown).
integer
ID of an existing comment to reply to, creating a threaded comment; if omitted, a top-level comment is created.
string
required
Workspace ID or slug (e.g., ‘my_workspace_slug’ or a UUID) for the Bitbucket workspace containing the snippet.
string
required
Unique, encoded ID of the Bitbucket snippet to comment on (typically part of the snippet’s URL).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_TEAMS_PIPELINES_CONFIG_VARIABLESCreates a workspace-level pipeline configuration variable in Bitbucket for the workspace identified by the supplied team username. Use to add environment variables or configuration values for pipelines in that workspace.

Input Parameters

string
required
The name/key of the pipeline variable. Must be unique within the team’s pipeline configuration.
string
required
The value of the pipeline variable. This will be available to all pipelines in the team.
boolean
Whether the variable should be secured (masked in logs). Set to True for sensitive values like passwords or API keys, False for non-sensitive values.
string
required
The team username that owns the pipeline configuration. This is the team identifier in Bitbucket.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_CREATE_USERS_PIPELINES_CONFIG_VARIABLESCreates 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.

Input Parameters

string
required
The name/key of the pipeline variable. Must be unique for the user.
string
required
The value of the pipeline variable.
boolean
Whether the variable should be secured/encrypted (true) or stored as plain text (false). Defaults to false.
string
required
The username or UUID of the user. Can be a username (e.g., ‘myusername’) or a UUID enclosed in curly braces (e.g., ‘{4f3ecac3-c951-41d4-8a4c-95f40be978fc}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DECLINE_PULL_REQUESTDecline a Bitbucket Cloud pull request via the REST API. Use this action when you need to reject a pull request that should not be merged. This action is irreversible — once declined, the pull request cannot be reopened and must be recreated if needed.

Input Parameters

string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to decline.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_COMMIT_COMMENTPermanently deletes a specific comment on a commit. Use when removing outdated, incorrect, or unwanted feedback on a commit.

Input Parameters

string
required
The commit hash (SHA) or commit reference. This identifies the commit that has the comment to be deleted.
string
required
The slug of the repository. This is the repository’s name, usually in lowercase and with hyphens instead of spaces.
string
required
The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.
string
required
The unique identifier of the comment to be deleted from the specified commit.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_ISSUEPermanently deletes a specific issue, identified by its issue_id, from the repository specified by repo_slug within the given workspace.

Input Parameters

string
required
The unique identifier of the issue to be deleted from the specified repository.
string
required
The slug of the repository. This is the repository’s name, usually in lowercase and with hyphens instead of spaces.
string
required
The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_PULL_REQUEST_COMMENTPermanently deletes a specific pull request comment (top-level, inline, or threaded reply). Use when removing outdated, incorrect, or unwanted feedback from a pull request.

Input Parameters

string
required
The slug of the repository. This is the repository’s name, usually in lowercase and with hyphens instead of spaces.
string
required
The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.
integer
required
The unique identifier of the comment to be deleted from the pull request. This can be a top-level comment, inline comment, or threaded reply.
integer
required
The unique identifier of the pull request containing the comment to be deleted.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONSDeletes 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.

Input Parameters

string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
The unique identifier of the report that contains the annotation.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.
string
required
The unique identifier of the annotation to delete.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_REPOSITORYPermanently deletes a specified Bitbucket repository; this action is irreversible and does not affect forks.

Input Parameters

string
required
The slug (URL-friendly name) of the repository to be deleted. This identifies the repository within the workspace.
string
required
The ID or slug of the Bitbucket workspace that owns the repository. This can be a user’s username or a team’s slug.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_SNIPPETS_WATCHStops watching a specific snippet. Use when you want to unsubscribe from notifications for a snippet.

Input Parameters

string
required
The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace.
string
required
The unique identifier (encoded ID) of the snippet to stop watching.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DELETE_USER_PIPELINE_VARIABLEPermanently 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.

Input Parameters

string
required
The username of the Bitbucket account that owns the pipeline variable. This is the account identifier.
string
required
The UUID of the pipeline variable to delete. This must be in UUID format (e.g., b070fa8a-c3db-42bd-870c-dea7c980c7b8) and can be optionally wrapped in curly braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_DOWNLOAD_REPOSITORY_ARCHIVEDownload a repository revision as a zip, gzip, or bzip2 archive.

Input Parameters

string ("zip" | "gz" | "bz2")
Archive compression format.
string
required
Branch, tag, or commit hash to archive.
string
required
Repository slug or UUID.
string
required
Workspace slug or UUID.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_BRANCHRetrieves 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.

Input Parameters

string
required
The name of the branch to retrieve (e.g., ‘master’, ‘main’, ‘feature/my-feature’). Do not include the ‘refs/heads/’ prefix.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_COMMIT_BUILD_STATUSGet 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.

Input Parameters

string
required
The unique key identifying the specific build status.
string
required
The commit hash to get the build status for.
string
required
The slug or UUID of the repository.
string
required
The workspace ID or slug that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_COMMIT_CHANGESTool 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.

Input Parameters

integer
Page number for paginated results (starts from 1).
string
required
Commit SHA or range (e.g., ‘3a8b42’ for single commit or ‘3a8b42..9ff173’ for range).
integer
Number of changes per page (1-100). Bitbucket default is 500 if not specified.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_COMMIT_COMMENTRetrieves 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.

Input Parameters

string
required
The commit hash to retrieve the comment from.
string
required
The repository slug (URL-friendly name).
string
required
The workspace slug or UUID that owns the repository.
integer
required
The unique identifier for the comment.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_COMMIT_DIFFTool 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.

Input Parameters

string
Optional file path to filter the diff to a specific file or directory. If omitted, returns diff for all changes.
string
required
A commit SHA, branch name, tag, or revspec (e.g. ‘3a8b42..9ff173’ for range). For a single commit, provide the commit hash. For comparing two commits, use ‘commit1..commit2’ format.
boolean
Whether to generate merge diff. Set to true for merge commit diffs.
boolean
Whether to generate a 2-way three-dot diff when spec contains two commits. Set to true to use three-dot diff notation.
boolean
Whether to include binary file diffs. Set to true to include binary diffs in the output.
integer
Number of context lines to include around changes. If not specified, uses the default context lines.
boolean
Whether to detect file renames. Set to true to show rename detection in the diff.
string
required
The repository slug (URL-friendly name).
string
required
The workspace ID or username that owns the repository.
boolean
Whether to ignore whitespace changes in the diff. Set to true to exclude whitespace-only changes.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_CURRENT_USER2Tool 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.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_DEPLOYMENT_ENVIRONMENT_VARIABLESRetrieves deployment environment level variables for a specific Bitbucket repository environment. Use when you need to view or audit environment-specific configuration variables for deployments.

Input Parameters

string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.
string
required
The UUID of the deployment environment. Must be provided with curly braces (e.g., {2e1c3c19-12f2-4e9b-9ed7-45512af9a7ce}). The API will handle URL-encoding automatically.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_FILE_FROM_REPOSITORYRetrieves 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.

Input Parameters

string
required
Full path to the file within the repository (e.g., ‘src/main.py’).
string
required
Commit hash, branch name (fetches latest), or tag for the file version.
string
required
Repository slug or UUID (typically URL-formatted name).
string
required
Workspace ID or UUID (often username or team name) containing the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_HOOK_EVENTSRetrieves 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.

Input Parameters

string ("repository" | "workspace")
required
The type of entity for which to retrieve available webhook events. Use ‘repository’ for repository-level events or ‘workspace’ for workspace-level events. Note: team and user webhooks are deprecated; use workspace instead.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_OPENID_CONFIGURATIONRetrieves 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.

Input Parameters

string
required
The workspace identifier (workspace slug or UUID). This identifies the Bitbucket workspace for which to retrieve the OIDC configuration.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PIPELINE_STEPRetrieve one pipeline step and its available execution details by UUID.

Input Parameters

string
required
Repository slug or UUID containing the pipeline.
string
required
UUID of the pipeline step to retrieve, including braces.
string
required
Workspace slug or UUID that owns the repository.
string
required
Pipeline UUID, including braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PIPELINE_STEP_LOGRetrieve all or a bounded byte range of one pipeline step’s execution log.

Input Parameters

integer
Last byte to return, inclusive. Must be provided with range_start and be greater than or equal to it.
string
required
Repository slug or UUID.
string
required
UUID of the pipeline step whose log should be retrieved.
string
required
Workspace slug or UUID that owns the repository.
integer
First byte to return. Must be provided with range_end.
string
required
Pipeline UUID or build number.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUESTGet a single pull request by ID, returning its modeled details.

Input Parameters

string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name). Must exactly match the pull request’s workspace (case-sensitive); slug and UUID are not interchangeable.
integer
required
The ID of the pull request to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_ACTIVITYReturn one pull request’s comments, updates, approvals, and change requests.

Input Parameters

integer
Page number to retrieve. Page numbering starts at 1.
integer
Number of activity entries to return per page (1-50).
string
required
Repository slug or UUID containing the pull request.
string
required
Workspace slug or UUID that owns the repository.
integer
required
Repository-scoped numeric pull request ID.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_COMMENTTool 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.

Input Parameters

string
required
The repository slug (URL-friendly name).
string
required
The workspace slug or UUID that owns the repository.
integer
required
The unique identifier for the comment.
integer
required
The unique identifier of the pull request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_COMMITSTool 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.

Input Parameters

integer
Number of commits per page (1-100).
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to retrieve commits for.
string ("minimal" | "full")
Level of detail in the response. ‘minimal’ (default) returns only essential commit information (hash, message, date, author name/email, html_link). ‘full’ returns the complete Bitbucket API response with all nested objects.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_DIFFTool 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.

Input Parameters

integer
Maximum number of characters to return in the diff. If the diff exceeds this limit, it will be truncated. If None, no truncation is applied. Use this to protect against very large diffs.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to retrieve the diff for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_DIFFSTATGet a paginated diffstat for a Bitbucket pull request, showing changed files and their change statistics, including lines added, lines removed, and status.

Input Parameters

integer
Page number for paginated results (starts from 1).
integer
Number of diffstat entries per page (1-100). Bitbucket default is 500 if not specified.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to get diffstat for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_PULL_REQUEST_MERGE_BASEResolve a pull request’s refs and return their best common ancestor commit when the source and destination are in the same repository.

Input Parameters

string
required
Repository slug or UUID containing the pull request.
string
required
Workspace slug or UUID that owns the repository.
integer
required
Positive repository-scoped pull request ID.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_RAW_FILE_CONTENTDEPRECATED: Use BITBUCKET_GET_FILE_FROM_REPOSITORY instead. 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.

Input Parameters

string
required
The file path including filename and extension (e.g., ‘src/main.py’ or ‘README.md’).
string
required
The commit SHA, branch name, or tag name to retrieve the file from.
string
required
The repository slug (URL-friendly name) where the file is located.
string
required
The workspace ID or username that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_BRANCHING_MODELReturn 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.

Input Parameters

string
required
The repository slug.
string
required
This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMITTool 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.

Input Parameters

string
required
The commit hash (SHA) to retrieve.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMIT_COMMENTSRetrieves a page of comments on a specific commit in a Bitbucket repository, including global and inline code comments. Use it to view feedback, discussions, or notes on the commit.

Input Parameters

integer
Page number for pagination. Defaults to 1 if not specified.
string
required
The commit hash/SHA to retrieve comments for.
integer
Number of items per page for pagination. Defaults to 10 if not specified.
string
required
The slug (URL-friendly version) of the repository name.
string
required
The ID or slug of the workspace that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMIT_REPORTReturns 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.

Input Parameters

string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
Either the uuid or external-id of the report to retrieve.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMIT_REPORTSTool 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.

Input Parameters

string
required
The commit hash to retrieve reports for.
string
required
The repository slug (URL-friendly name).
string
required
The workspace ID or slug that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONSReturns 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.

Input Parameters

string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
Either the uuid or external-id of the report that contains the annotation.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.
string
required
Either the uuid or external-id of the annotation to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_COMMIT_STATUSESReturns a page of build statuses, such as CI/CD pipeline results, for a specific commit. Use it to check build status or monitor pipeline results for that commit.

Input Parameters

string
required
The commit hash (SHA) to retrieve statuses for. Can be full or abbreviated hash.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_EFFECTIVE_BRANCHING_MODELRetrieves 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.

Input Parameters

string
required
The repository slug. This is usually the repository’s name in URL-friendly format.
string
required
The workspace slug or UUID that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_ENVIRONMENTS2Retrieve 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.

Input Parameters

string
required
The slug or UUID of the repository.
string
required
The workspace ID or slug that owns the repository.
string
required
The UUID of the environment to retrieve. Must include curly braces (e.g., {2e1c3c19-12f2-4e9b-9ed7-45512af9a7ce}).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_FILEHISTORYReturns 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.

Input Parameters

string
Query string for filtering commits in the file history. Common use: filter by commit date using ‘commit.date<=YYYY-MM-DD’ or ‘commit.date>=YYYY-MM-DD’. Example: ‘commit.date<=2024-12-31’ returns only commits before that date.
integer
Page number for paginated results (starts from 1).
string
required
Full path to the file within the repository (e.g., ‘README.md’, ‘src/main.py’).
string
required
Commit hash, branch name, or tag from which to retrieve file history. The API returns commits reachable from this reference that modified the file.
string
Comma-separated list of fields to include or exclude from the response. Prefix with ’+’ to add fields or ’-’ to remove them. Example: ‘+values.commit.message’ adds commit messages to the response.
integer
Number of commits per page (1-100). Default is typically 30 if not specified.
boolean
Whether to follow file renames through history. If true (default), returns commits that modified the file even if it had a different name. If false, only returns commits where the file had the current path.
string
required
The repository slug (URL-friendly name) or UUID.
string
required
The workspace slug or UUID that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_ISSUES_VOTETool 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.

Input Parameters

integer
required
The numeric ID of the issue to check vote status for.
string
required
The slug (URL-friendly name) of the repository.
string
required
The workspace ID or slug (URL-friendly name) that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_MERGE_BASEGet 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.

Input Parameters

string
required
Two commit hashes separated by ’..’ (e.g., ‘3a8b42..9ff173’ or ‘abc123..def456’). This specifies the two commits to find the best common ancestor between.
string
required
The slug or UUID of the repository.
string
required
The workspace ID or slug that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES2Retrieve 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.

Input Parameters

string
required
The repository slug (URL-friendly name) or UUID.
string
required
The workspace ID (slug) or workspace UUID that owns the repository.
string
required
The pipeline UUID to retrieve. Must be in UUID format, typically enclosed in curly braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_CACHESRetrieves a page of pipeline caches for a specific Bitbucket repository.

Input Parameters

string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_RUNNERSRetrieves the list of self-hosted runners configured for a repository’s pipelines. Use when you need to view available runners for pipeline execution.

Input Parameters

string
required
The repository slug (URL-friendly identifier) for the repository.
string
required
The workspace slug or UUID that owns the repository. This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_SCHEDULESRetrieves configured pipeline schedules for a Bitbucket repository. Use when you need to view scheduled pipeline runs and their cron patterns.

Input Parameters

string
required
The slug or identifier of the repository.
string
required
The workspace ID or slug that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_SSH_KNOWN_HOSTSRetrieves 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.

Input Parameters

string
required
The repository slug (URL-friendly identifier) for the repository.
string
required
The workspace slug or UUID. This identifies the Bitbucket workspace that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_CONFIG_VARIABLESRetrieves 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.

Input Parameters

string
Query string for filtering results using Bitbucket Query Language (BBQL).
integer
Page number for pagination. Use this to retrieve subsequent pages of results.
string
Field to sort results by. Prefix with a hyphen (-) for descending order.
integer
Number of items to return per page. Controls the size of the paginated response.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PIPELINES_STEPSRetrieves a page of steps for a given pipeline, including available state, duration, and command details.

Input Parameters

string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.
string
required
The UUID of the pipeline. Must be enclosed in curly braces (e.g., ‘{f5500ca2-b74d-4e6a-84bf-5d2f73695152}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_ACTIVITYGets a paginated activity log for pull requests in a repository, including comments, updates, and approvals.

Input Parameters

string
Opaque continuation cursor: copy the ctx query value from the returned next URL. Keep the same workspace, repo_slug, and pagelen; omit page unless it appears in that URL. Omit ctx for the first page.
integer
Page number for paginated results (starts from 1). For continuation, copy ctx from the returned next URL rather than incrementing page.
integer
Number of activity entries per page (1-50). Bitbucket default is 20 if not specified.
string
required
The repository slug (URL-friendly name).
string
required
The workspace ID or slug (URL-friendly name).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_COMMENTSRetrieves 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.

Input Parameters

integer
Page number for pagination. Defaults to 1 if not specified.
string
Sort order for results. Default is oldest to newest. Use ‘-created_on’ for newest to oldest.
integer
Number of items per page for pagination. Defaults to 10 if not specified.
string
required
The slug (URL-friendly version) of the repository name.
string
required
The ID or slug of the workspace that owns the repository.
integer
required
The pull request ID to retrieve comments for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_PULLREQUESTS_STATUSESReturns a page of build statuses for a specific pull request, such as CI/CD pipeline results. Use it to check build status or monitor pull request checks.

Input Parameters

integer
Page number for paginated results (starts from 1).
integer
Number of statuses per page (1-100). Bitbucket default is 30 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.
integer
required
The ID of the pull request to retrieve statuses for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_REFSReturns a paginated list of branches and tags in a repository, with optional query filtering by type, name pattern, or commit hash.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter refs. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal). String values MUST be enclosed in double quotes. Filter by name pattern using ‘name”pattern”’, by type using ‘type=“branch”’ or ‘type=“tag”’, or by commit hash using ‘target.hash=“hash”’. Examples: ‘name~“feature/”’ (refs starting with feature/), ‘type=“branch”’ (only branches), ‘type=“tag”’ (only tags), ‘target.hash=“a1b2c3d4”’ (refs pointing to specific commit). Combine multiple conditions with AND/OR (e.g., ‘type=“branch” AND name~“feature/”’).
integer
Page number for paginated results (starts from 1).
string
Field for sorting ref results. Prefix with ’-’ for descending order. Common sortable fields: ‘name’, ‘target.date’ (commit date). Default sorting applies natural sorting for ref names with numeric values.
integer
Number of refs per page (1-100). Bitbucket default is typically 10 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_REFS_TAGSRetrieves 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.

Input Parameters

string
required
The name of the tag to retrieve (without refs/tags/ prefix). For example, ‘v1.0.0’ or ‘fedex17’.
string
required
The slug (URL-friendly name) of the repository. This identifies the repository within the workspace.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_SRCLists 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.

Input Parameters

string
Optional format parameter. Use ‘meta’ to get metadata instead of raw contents when accessing files.
string
required
The repository slug (URL-friendly repository name).
string
required
The workspace ID or slug that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORIES_WATCHERSRetrieves a paginated list of all the watchers on the specified repository. Use when you need to see who is watching a particular repository.

Input Parameters

string
required
The repository slug (URL-friendly identifier) for the repository.
string
required
The workspace ID or slug that owns the repository. This is the user-friendly identifier or UUID for the workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORYRetrieves detailed information about a specific repository in a Bitbucket workspace. Use when you need to get repository metadata, settings, or details.

Input Parameters

string
required
The repository slug (URL-friendly identifier) for the repository to retrieve.
string
required
The workspace slug or UUID. This identifies the Bitbucket workspace that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_REPOSITORY_PATCHRetrieves the Git patch for a Bitbucket repository at a specified revision or commit range in unified diff format. An optional character limit can truncate the patch; the response reports whether truncation occurred.

Input Parameters

string
required
A commit hash, branch name, tag, or commit range (e.g., ‘3a8b42..9ff173’). If a single commit is provided, the diff is against its first parent. For ranges, shows diff between the two commits.
integer
Maximum number of characters to return in the patch. If the patch exceeds this limit, it will be truncated. If None, no truncation is applied. Use this to protect against very large patches.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_SNIPPETRetrieves a specific Bitbucket snippet by its encoded ID from an existing workspace, returning its metadata and file structure.

Input Parameters

string
required
The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace.
string
required
The unique identifier (encoded ID) of the snippet to be retrieved.
string
The desired format for the response. Valid options are ‘application/json’, ‘multipart/related’, or ‘multipart/form-data’. This may affect how snippet content or file data is presented.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_SNIPPETS_WATCHChecks if the current user is watching a specific snippet. Use when you need to verify watch status for a snippet.

Input Parameters

string
required
The workspace ID (slug) or the workspace UUID surrounded by curly braces, identifying the Bitbucket workspace.
string
required
The unique identifier (encoded ID) of the snippet to check watch status for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_SSH_LATEST_KEYSRetrieves 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.

Input Parameters

integer
The page number for pagination. Starts at 1.
integer
Number of SSH keys to return per page. Default is typically 10.
string
required
The username of the Bitbucket user to retrieve SSH keys for. This is the account username (slug), not the display name or UUID.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USERRetrieves 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.

Input Parameters

string
required
The username or UUID of the user to retrieve. Can be a username (e.g., ‘john_doe’) or a UUID enclosed in curly braces (e.g., ‘{4f3ecac3-c951-41d4-8a4c-95f40be978fc}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USER_EMAILSRetrieves a page of the authenticated user’s email addresses, including confirmed and unconfirmed addresses, with pagination links when provided.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USER_EMAILS2Retrieves 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.

Input Parameters

string
required
The email address to retrieve details for. Must be one of the authenticated user’s email addresses.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USER_PERMISSIONS_REPOSITORIESRetrieves a page of repository permissions for repositories the authenticated user has explicit access to, including permission levels. Supports pagination.

Input Parameters

integer
Page number for paginated results. Used to retrieve a specific page in a multi-page result set. Page numbers start at 1.
integer
Number of items to return per page for pagination. Controls the size of the paginated result set. Default is typically 10 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USER_PERMISSIONS_WORKSPACESRetrieves a page of workspace memberships and permission levels for the authenticated user, including their effective role. Supports filtering and pagination.

Input Parameters

string
Query string to filter results by workspace slug or permission level using Bitbucket’s filtering syntax. Examples: q=workspace.slug=“workspace1” or q=permission=“owner”. Supported fields: workspace.slug (workspace identifier), permission (permission level). Use exact match with = operator. String values must be enclosed in double quotes.
integer
Page number for pagination. Use this to navigate through multiple pages of results.
integer
Number of items per page for pagination. Controls how many workspace permission objects are returned in a single response.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_USER_WORKSPACESRetrieves a page of workspaces accessible to the authenticated user, optionally filtered by workspace slug or permission level. The response may include a link to the next page.

Input Parameters

string
Query string to filter workspaces by attributes such as workspace slug or permission level. Examples: ‘workspace.slug=“my-workspace”’ or ‘permission=“owner”’. Follow Bitbucket’s filtering syntax for complex queries.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_WORKSPACERetrieves detailed information about a specific Bitbucket workspace. Use when you need to get workspace metadata, settings, or details.

Input Parameters

string
required
The workspace ID (slug) or workspace UUID surrounded by curly-braces. Example: ‘my-workspace’ or ‘{workspace-uuid}’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_WORKSPACES_PULLREQUESTSRetrieves a page of workspace pull requests filtered by author and optionally by state across repositories. Results may be incomplete if a repository’s pull request request fails; pagination links are not provided.

Input Parameters

integer
Page number for paginated results (starts from 1).
string ("OPEN" | "MERGED" | "DECLINED")
Lifecycle state of a pull request.
integer
Number of pull requests per page (1-100). Bitbucket default is 10 if not specified.
string
required
Workspace ID or slug (URL-friendly name).
string
required
The username of the user whose pull requests you want to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_GET_WORKSPACES_SEARCH_CODETool 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.

Input Parameters

integer
Page number for pagination. Use this to navigate through multiple pages of search results.
string
Additional fields to include in the response, using the fields parameter syntax. For example, ‘+values.file.commit.repository’ to include repository details for each code match.
integer
Number of results per page. Controls how many code search results are returned in a single response.
string
required
The workspace identifier. This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’).
string
required
The search query string to search for in the code. Can use advanced syntax like ‘foo+repo:demo’ to search within specific repositories, or ‘test+ext:py’ to filter by file extension.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_BRANCHESLists 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.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter branches. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal). String values MUST be enclosed in double quotes. Common use case: filter by branch name pattern using ‘name”pattern”’. Examples: ‘name~“feature/”’ (branches starting with feature/), ‘name=“main”’ (exact match for main branch). Combine multiple conditions with AND/OR (e.g., ‘name~“feature/” OR name~“bugfix/”’).
integer
Page number for paginated results (starts from 1).
string
Field for sorting branch results. Prefix with ’-’ for descending order. Common sortable fields: ‘name’, ‘target.date’ (commit date). Default sorting applies natural sorting for branch names with numeric values.
integer
Number of branches per page (1-100). Bitbucket default is typically 10 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_COMMITSTool 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.

Input Parameters

integer
Page number for paginated results (starts from 1).
string
Filter commits to only those that affect the specified file or directory path.
string
Branch or tag name, or commit SHA to exclude from the commit history. Commits reachable from this ref will be excluded. Multiple values can be separated by commas.
string
Branch or tag name, or commit SHA to include in the commit history. If not specified, the repository’s default branch is used. Multiple values can be separated by commas (e.g., ‘main,develop’).
integer
Number of commits per page (1-100). Bitbucket default is typically 30 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_COMMITS_FROM_REVISIONTool 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.

Input Parameters

integer
Page number for paginated results (starts from 1).
string
Optional file path to filter commits. Only commits that modified this file or directory will be returned.
string
Optional commit hash or branch to exclude from the results. Can be used to create a range with the ‘include’ parameter.
string
Optional commit hash or branch to include in the results. Can be used to create a range with the ‘exclude’ parameter.
integer
Number of commits per page (1-100). Bitbucket default is typically 30 if not specified.
string
required
The commit hash, branch name, tag, or other revision identifier to start listing commits from. Commits are returned in reverse chronological order starting from this revision.
string
required
The slug of the repository. This is the repository’s name, usually in lowercase and with hyphens instead of spaces.
string
required
The workspace ID (slug) or UUID of the Bitbucket workspace that owns the repository. This can be the workspace name or its universally unique identifier.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_COMMITS_ON_MASTERLists 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.

Input Parameters

integer
Page number for paginated results (starts from 1).
integer
Number of commits per page (1-100). Bitbucket default is typically 30 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_DEPLOYMENTSLists deployments for a specified Bitbucket repository. Use when you need to view deployment history and status across environments.

Input Parameters

string
Query string for filtering deployment results using Bitbucket Query Language (BBQL). Use operators like ’=’ for exact match, ’~’ for contains, ’!=’ for not equal.
integer
Page number of the results to retrieve. Defaults to 1 if not specified.
string
Field designation for sorting results. Prefix with ’-’ for descending order.
integer
Number of results per page (1-100). Defaults to the Bitbucket API’s default page length if not specified.
string
required
The repository slug (URL-friendly name).
string
required
The workspace ID or slug (URL-friendly name). This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_ISSUESLists 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.

Input Parameters

string
Filter issues by kind (type). Use ‘bug’, ‘enhancement’, ‘proposal’, or ‘task’. If not provided, issues of all kinds are returned.
integer
Page number for paginated results (starts from 1).
string
Filter issues by state. Use a specific state like ‘new’, ‘open’, ‘resolved’, ‘on hold’, ‘invalid’, ‘duplicate’, ‘wontfix’, or ‘closed’. If not provided, all issues regardless of state are returned.
integer
Number of issues per page (1-100). Bitbucket default is 10 if not specified.
string
Filter issues by assignee. Provide the Bitbucket account ID (UUID) of the assignee. Use ‘null’ (as a string) to find unassigned issues. If not provided, issues with any assignee (or no assignee) are returned.
string
Filter issues by priority. Use ‘trivial’, ‘minor’, ‘major’, ‘critical’, or ‘blocker’. If not provided, issues of all priorities are returned.
string
required
The slug (URL-friendly name) of the repository.
string
required
The workspace ID or slug (URL-friendly name) that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PIPELINESList pipelines in a Bitbucket repository, returning pipeline metadata including state, trigger, and build seconds used. Use to browse pipeline history or check pipeline status.

Input Parameters

integer
Page number for paginated results (starts from 1).
integer
Number of pipelines per page (1-100). Bitbucket default is typically 10 if not specified.
string
required
The repository slug (URL-friendly identifier).
string
required
The workspace slug or UUID that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PIPELINE_STEP_TEST_CASESReturn test cases discovered for one pipeline step, including failures and durations.

Input Parameters

integer
Page number to retrieve. Page numbering starts at 1.
integer
Maximum number of test cases to return on this page.
string
required
Repository slug or UUID containing the pipeline.
string
required
Pipeline step UUID, including braces.
string
required
Workspace slug or UUID that owns the repository.
string
required
Pipeline UUID, including braces, or pipeline build number.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PULL_REQUEST_MERGEABILITY_CHECKSReturn Bitbucket’s current pre-merge checks for one pull request. The result is not exhaustive because Bitbucket cannot evaluate every merge condition before attempting the merge. Use each check’s blocking field, not status alone, to determine whether it currently prevents merging.

Input Parameters

string
required
Repository slug or UUID containing the pull request.
string
required
Workspace slug or UUID that owns the repository.
integer
required
Positive repository-scoped pull request ID.
boolean
Skip the expensive Git conflict evaluation.
boolean
Skip the expensive maximum-commits-behind ancestry check.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PULL_REQUESTSLists pull requests in a specified, accessible Bitbucket repository, optionally filtering by state (OPEN, MERGED, DECLINED).

Input Parameters

integer
Page number for paginated results (starts from 1).
string ("OPEN" | "MERGED" | "DECLINED")
Lifecycle state of a pull request.
integer
Number of pull requests per page (1-50). Bitbucket default is 10 if not specified.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PULL_REQUESTS_FOR_COMMITList pull requests in which a repository commit was reviewed. Requires Bitbucket’s Pull Request Commit Links app to be installed and the repository to be indexed.

Input Parameters

integer
Page number to retrieve. Page numbering starts at 1.
string
required
SHA1 hash of the commit whose related pull requests to list.
integer
Number of pull requests to return per page (1-100).
string
required
Repository slug or UUID containing the commit.
string
required
Workspace slug or UUID that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_PULL_REQUEST_TASKSLists a page of tasks associated with a pull request in a Bitbucket repository, with pagination metadata.

Input Parameters

integer
Page number for paginated results (starts from 1).
integer
Number of tasks per page (1-100). Bitbucket default is 10 if not specified.
string
required
The slug (URL-friendly name) of the repository.
string
required
The workspace ID or slug (URL-friendly name) that owns the repository.
integer
required
The unique identifier of the pull request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_REPOSITORIESRetrieves 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.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter repositories. Note: This parameter requires the ‘role’ parameter to be specified. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal), ’>’ ’>=’ ’<’ ’<=’ (comparison for dates/numbers). String values MUST be enclosed in double quotes. Valid repository fields: ‘name’, ‘full_name’, ‘is_private’, ‘created_on’, ‘updated_on’, ‘language’. Combine multiple conditions with AND/OR (e.g., ‘name”api” AND is_private=false’).
integer
The page number to retrieve in the paginated list of results. Page numbering starts at 1. Use together with ‘pagelen’ to control pagination.
string ("member" | "contributor" | "admin" | "owner")
Enum for repository role filter values.
string
Field to sort returned repositories by. Prefix with a hyphen (-) for descending order. Common sortable fields: ‘name’, ‘created_on’, ‘updated_on’.
string
ISO-8601 timestamp to filter results created after this date/time. Format: YYYY-MM-DDTHH:mm:ss.sssZ (e.g., ‘2024-01-01T00:00:00.000Z’). Only repositories created after this timestamp will be returned.
integer
The number of items to return per page. Accepts values between 1 and 100 (inclusive). Defaults to 10 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_REPOSITORIES_ENVIRONMENTSLists a page of deployment environments configured for a Bitbucket repository, with optional filtering and sorting. Use it to view available environments, check their configurations, or select one for deployment operations.

Input Parameters

string
Query string for filtering environment results using Bitbucket Query Language (BBQL). Use operators like ’=’ for exact match, ’~’ for contains, ’!=’ for not equal.
integer
Page number of the results to retrieve. Defaults to 1 if not specified.
string
Field designation for sorting results. Prefix with ’-’ for descending order.
integer
Number of results per page (1-100). Defaults to the Bitbucket API’s default page length if not specified.
string
required
The repository slug (URL-friendly name) or UUID.
string
required
The workspace ID or slug that owns the repository. This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACELists repositories in a specified Bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results. Responses are paginated; iterate using the next field in each response until it is absent to retrieve all repositories.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter repositories. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal), ’>’ ’>=’ ’<’ ’<=’ (comparison for dates/numbers). String values MUST be enclosed in double quotes. Valid repository fields: ‘name’, ‘full_name’, ‘project.key’, ‘is_private’, ‘created_on’, ‘updated_on’, ‘language’. Combine multiple conditions with AND/OR (e.g., ‘name”api” AND is_private=true’). Note: ‘repository’ is NOT a valid field name - use ‘name’ instead. Invalid or malformed expressions return empty results silently rather than an error.
integer
Page number of the results to retrieve. Defaults to 1 if not specified.
string
Filters repositories by the authenticated user’s role within each repository.
string
Field for sorting repository results. Prefix with ’-’ for descending order. Common sortable fields: ‘name’, ‘updated_on’, ‘created_on’.
integer
Number of results per page (1-100). Defaults to 10 if not specified.
string
required
The identifier of the Bitbucket workspace. This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’). Empty results may indicate insufficient permissions rather than an invalid identifier.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_REPOSITORY_FORKSRetrieves a paginated list of all forks for a specific repository in a Bitbucket workspace. Returns repository objects for each fork with metadata like owner, creation date, and size. Use this action when you need to discover who has forked a repository or analyze fork relationships.

Input Parameters

integer
The page number to retrieve in the paginated list of results. Page numbering starts at 1. Use together with ‘pagelen’ to control pagination.
integer
The number of items to return per page. Accepts values between 1 and 100 (inclusive).
string
required
The repository slug (URL-friendly identifier) for the repository whose forks to list.
string
required
The workspace slug or UUID that owns the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_REPOSITORY_PATHSLists 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.

Input Parameters

string
Filter query string using Bitbucket’s REST API filtering syntax to narrow results.
integer
Page number for paginated results (starts from 1).
string
Directory path within the repository to list. Use empty string for root. Must be a directory, not a file.
string
Field name for sorting results. Prefix with ’-’ for descending order.
string
required
Commit hash, branch name, or tag to list paths from. Determines the revision to traverse.
integer
Number of entries per page (1-100). Controls pagination size.
integer
Maximum depth for breadth-first recursive directory traversal. If specified, includes nested subdirectories up to this depth.
string
required
Repository slug or UUID (typically URL-formatted name).
string
required
Workspace ID or UUID (often username or team name) containing the repository.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_SNIPPETSLists a page of snippets accessible to the authenticated user, optionally filtered by role (owner, contributor, or member). Pagination parameters select the page and page size.

Input Parameters

integer
Page number of the results to retrieve. Defaults to 1 if not specified.
string ("owner" | "contributor" | "member")
Enum for snippet role filter values.
integer
Number of results per page (1-100). Defaults to the Bitbucket API’s default page length if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_TAGSLists 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.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter tags. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal). String values MUST be enclosed in double quotes. Common use case: filter by tag name pattern using ‘name”pattern”’ or by commit hash using ‘target.hash=“hash”’. Examples: ‘name~“v1.”’ (tags starting with v1.), ‘name=“v1.0.0”’ (exact match for v1.0.0 tag), ‘target.hash=“a1b2c3d4”’ (tags pointing to specific commit). Combine multiple conditions with AND/OR (e.g., ‘name~“v1.” OR name~“v2.”’).
integer
Page number for paginated results (starts from 1).
string
Field for sorting tag results. Prefix with ’-’ for descending order. Common sortable fields: ‘name’, ‘target.date’ (commit date). Default sorting applies natural sorting for tag names with numeric values.
integer
Number of tags per page (1-100). Bitbucket default is typically 10 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_VERSIONSLists 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.

Input Parameters

string
Query string using Bitbucket Query Language (BBQL) to filter versions. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal). String values MUST be enclosed in double quotes. Common use case: filter by version name pattern using ‘name”pattern”’. Examples: ‘name~“1.”’ (versions starting with 1.), ‘name=“2.0”’ (exact match for version 2.0).
integer
Page number for paginated results (starts from 1).
string
Field for sorting version results. Prefix with ’-’ for descending order. Common sortable fields: ‘name’. Default sorting applies natural sorting.
integer
Number of versions per page (1-100). Bitbucket default is typically 10 if not specified.
string
required
The slug or UUID of the repository. This is usually the repository’s name in URL-friendly format.
string
required
The workspace ID or slug that owns the repository. This can typically be found in the URL of your Bitbucket workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_WORKSPACE_MEMBERSLists members of a specified Bitbucket workspace, returning one page of results.

Input Parameters

integer
Page number of the results to retrieve. Defaults to 1 if not specified.
integer
Number of results per page (1-100). Defaults to the Bitbucket API’s default page length if not specified.
string
required
The workspace ID (UUID) or slug from which to list members. The slug is the user-friendly, URL-safe identifier for the workspace.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_WORKSPACE_PROJECTSLists projects in a specified Bitbucket workspace, returning a page of results with optional filtering and sorting.

Input Parameters

string
Query string to filter projects by attributes, following Bitbucket’s filtering syntax. Syntax: ‘field operator value’. Operators: ’=’ (exact match), '' (contains substring), ’!=’ (not equal). String values MUST be enclosed in double quotes. Valid project fields: ‘name’, ‘key’, ‘is_private’. Combine multiple conditions with AND/OR (e.g., ‘name”api” AND is_private=true’).
integer
Specifies which page of results to return. Page numbering starts at 1.
string
Field to sort returned projects by; prefix with a hyphen (-) for descending order. Common sortable fields: ‘name’, ‘key’, ‘created_on’, ‘updated_on’.
integer
Controls the number of items per page. Must be between 1 and 100.
string
required
The identifier of the Bitbucket workspace. This can be the workspace slug (e.g., ‘my-workspace’) or its UUID enclosed in curly braces (e.g., ‘{workspace-uuid}’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_LIST_WORKSPACESLists Bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted. Results are paginated; follow the next field in each response to retrieve subsequent pages until next is absent. When multiple workspaces are returned, verify the correct slug or UUID before passing to downstream tools.

Input Parameters

string
Query string to filter workspaces by attributes, following Bitbucket’s filtering syntax.
integer
Page number of the results to retrieve. Defaults to 1 if not specified.
string
Field to sort returned workspaces by; prefix with a hyphen (-) for descending order.
integer
Number of results per page (1-100). Defaults to 10 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_MERGE_PULL_REQUESTMerge a Bitbucket Cloud pull request, with optional custom merge message, merge strategy, and source branch deletion. The merge may complete asynchronously, returning task details to check completion.

Input Parameters

string
Custom merge commit message. If not provided, Bitbucket generates a default message.
string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
string
Merge strategy to use. Common values include ‘merge_commit’, ‘squash’, ‘fast_forward’. If not specified, uses the repository’s default merge strategy.
integer
required
The ID of the pull request to merge.
boolean
Whether to close the source branch after merging. If not specified, uses the repository’s default setting.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_REQUEST_PULL_REQUEST_CHANGESTool 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.

Input Parameters

string
required
Repository slug (URL-friendly name).
string
required
Workspace ID or slug (URL-friendly name).
integer
required
The ID of the pull request to request changes on.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_RESOLVE_PULL_REQUEST_COMMENTTool to resolve or reopen a pull request comment thread. Use when marking a comment as addressed during review or reopening a previously resolved thread.

Input Parameters

string ("resolve" | "reopen")
Action to perform: ‘resolve’ marks the comment thread as addressed, ‘reopen’ unmarks it.
string
required
The repository slug (URL-friendly name).
string
required
The workspace slug or UUID that owns the repository.
integer
required
The unique identifier for the comment to resolve or reopen.
integer
required
The unique identifier of the pull request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_SEARCH_TEAM_CODESearch 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.

Input Parameters

integer
Which page of search results to retrieve (starts from 1).
integer
How many search results to retrieve per page (1-100). Default is 10 if not specified.
string
required
The team account username or UUID in curly braces (e.g., ‘team-name’ or ‘{team-uuid}’). Note: Teams endpoints are deprecated since Oct 2020; consider using workspace endpoints instead.
string
required
The search query string. Supports advanced syntax like ‘repo:demo’ to filter by repository, or combine terms with AND/OR operators. Same syntax as the Bitbucket UI search.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_SEARCH_USER_REPOSITORIES_CODETool 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.

Input Parameters

integer
Which page of search results to retrieve (default: 1).
string
Request additional fields in the response. Use ’+’ prefix to expand nested fields (e.g., ‘+values.file.commit.repository’ to include repository details).
integer
How many search results per page (default: 10).
string
required
The search query using the same syntax as the Bitbucket UI. Can include repo filters (e.g., ‘test’, ‘foo+repo:demo’).
string
required
The username of the user whose repositories to search.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_STOP_PIPELINESignal the stop of a pipeline and all of its steps that have not completed yet. This action is irreversible — once stopped, a pipeline cannot be restarted and must be re-triggered to run again. Use this action when you need to cancel a running pipeline execution that is no longer needed or was triggered incorrectly.

Input Parameters

string
required
The repository slug (URL-friendly name) or UUID.
string
required
The workspace ID (slug) or workspace UUID that owns the repository.
string
required
The pipeline UUID to stop. Must be in UUID format, typically enclosed in curly braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_INSIGHTS_PROJECTS_REPOS_COMMITS_REPORTSCreate 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.

Input Parameters

array
Array of data items containing additional information about the report. Maximum 6 items.
An external link providing more information about the report. Must be a valid HTTP/HTTPS URL.
string
required
The title of the report. Maximum 450 characters.
string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier (40 characters).
string ("PASSED" | "FAILED" | "PENDING")
Enum for report results.
string
required
Detailed description of the report. Maximum 2000 characters. Supports escaped newlines.
string
URL to the logo image for the reporting tool. Must be a valid HTTP/HTTPS URL.
string
The name of the system or tool that created the report. Maximum 450 characters.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
Unique identifier for the report. Recommend using reverse DNS namespacing (e.g., ‘com.company.tool.report-name’).
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.
string ("SECURITY" | "COVERAGE" | "TEST" | "BUG")
required
The type of report: SECURITY, COVERAGE, TEST, or BUG.
Whether remote link is enabled for the report.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_ISSUEUpdates an existing issue in a Bitbucket repository by modifying specified attributes; requires workspace, repo_slug, issue_id, and at least one attribute to update.

Input Parameters

string ("bug" | "enhancement" | "proposal" | "task")
Types/kinds of Bitbucket issues.
string ("new" | "open" | "resolved" | "on hold" | "invalid" | "duplicate" | "wontfix" | "closed")
States for Bitbucket issues.
string
The new title for the issue. If omitted, the title remains unchanged.
string
The new content or description for the issue, in raw text format. If omitted, the content remains unchanged.
string
The name of the version affected by this issue (e.g., ‘1.0.0’, ‘2.0-beta’). If omitted, the version remains unchanged.
string
required
The unique identifier (ID) of the issue to be updated.
string ("trivial" | "minor" | "major" | "critical" | "blocker")
Priority levels for Bitbucket issues.
string
The name of the component to associate with the issue (e.g., ‘API’, ‘Frontend’). If omitted, the component remains unchanged.
string
The name of the milestone to associate with the issue (e.g., ‘Sprint 1’, ‘v1.0 Launch’). If omitted, the milestone remains unchanged.
string
required
The slug or name of the repository (e.g., ‘my-app-repo’).
string
required
The workspace ID or slug that owns the repository (e.g., ‘my-company’ or ‘{123e4567-e89b-12d3-a456-426614174000}’).
string
The Bitbucket account ID (UUID) of the user to assign the issue to. If omitted, the assignee remains unchanged.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_PULL_REQUESTTool to update an existing pull request’s editable fields (e.g., title, description, reviewers) via the Bitbucket Cloud API. Use when you need to modify a pull request without creating a new one. Only sends fields that are explicitly provided to avoid accidental overwrites.

Input Parameters

boolean
If true, marks the pull request as a draft. If false, marks it as ready for review. If omitted, draft status remains unchanged.
string
Updated title for the pull request. If omitted, title remains unchanged.
string
required
Repository slug (URL-friendly name) or UUID.
array
Updated list of Bitbucket user UUIDs to be reviewers. Replaces existing reviewers. If omitted, reviewers remain unchanged.
string
required
Workspace ID (slug) or workspace UUID that owns the repository.
string
Updated Markdown description for the pull request. If omitted, description remains unchanged.
integer
required
Unique ID of the pull request to update.
boolean
If true, automatically closes the source branch upon pull request merge. If omitted, setting remains unchanged.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_REPOSITORIES_COMMIT_COMMENTSUpdates the contents of a comment on a commit. Use when you need to modify an existing comment’s text on a commit.

Input Parameters

string
required
The commit hash to update the comment on.
string
required
The repository slug (URL-friendly name).
string
required
The workspace slug or UUID that owns the repository.
string
required
The unique identifier for the comment to update.
string
required
The updated raw text content for the comment. Supports markdown formatting.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_REPOSITORIES_COMMIT_REPORTS_ANNOTATIONSCreates 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.

Input Parameters

integer
Line number in the file where the finding occurs. Must be a positive integer.
URL providing more information about the finding, such as documentation or issue tracker link.
string
File path where the annotation applies, relative to the repository root.
string
required
The commit hash to which the report belongs. This is the full SHA-1 commit identifier.
string ("PASSED" | "FAILED" | "IGNORED" | "SKIPPED")
Enumeration of annotation result statuses.
string
Extended description providing additional context, remediation guidance, or technical details about the finding.
string
required
Brief description of the finding. Should concisely explain what was detected.
string ("CRITICAL" | "HIGH" | "MEDIUM" | "LOW")
required
Impact level of the finding. CRITICAL for severe issues requiring immediate attention, HIGH for important issues, MEDIUM for moderate concerns, LOW for minor issues.
string
required
The repository slug (URL-friendly name) that contains the commit.
string
required
Either the uuid or external-id of the report that will contain the annotation.
string
required
The workspace ID or slug that owns the repository. This can be a user’s username or a team’s slug.
string
Unique identifier for tracking this annotation in an external system. Useful for correlating with external tools.
string
required
Either the uuid or external-id of the annotation to create or update.
string ("VULNERABILITY" | "CODE_SMELL" | "BUG")
required
Type of annotation indicating the nature of the finding: VULNERABILITY for security issues, CODE_SMELL for maintainability issues, or BUG for functional defects.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_TEAMS_PIPELINES_CONFIG_VARIABLESUpdates 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.

Input Parameters

string
required
The name/key of the pipeline variable. Must be unique within the team’s pipeline configuration.
string
required
The updated value of the pipeline variable. This will be available to all pipelines in the team.
boolean
Whether the variable should be secured (masked in logs). Set to True for sensitive values like passwords or API keys, False for non-sensitive values.
string
required
The team username that owns the pipeline configuration. This is the team identifier in Bitbucket.
string
required
The UUID of the pipeline variable to update. This must be in UUID format (e.g., 252a372b-3e5d-4869-9df5-c379d6b062e9) and can be optionally wrapped in curly braces.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: BITBUCKET_UPDATE_USERS_PIPELINES_CONFIG_VARIABLESUpdates 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.

Input Parameters

string
The updated name/key of the pipeline variable. If omitted, the key remains unchanged.
string
The updated value of the pipeline variable. If omitted, the value remains unchanged.
boolean
Whether the variable should be secured/encrypted (true) or stored as plain text (false). If omitted, the secured status remains unchanged.
string
required
The UUID or username of the user. When using UUID format, it should be URL-encoded (e.g., %7B4f3ecac3-c951-41d4-8a4c-95f40be978fc%7D for {4f3ecac3-c951-41d4-8a4c-95f40be978fc}).
string
required
The UUID of the pipeline variable to update. This can be obtained from the list or get variable endpoints.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not