Start free
ActionBitbucketUpdated June 2026

How do I list open PRs in Bitbucket?

Short answer: You can list pull requests in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket List Pull Requests action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 10 Bitbucket actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Workspace
workspace
stringRequiredWorkspace. Example: my-team
Repository Slug
repo_slug
stringRequiredRepository Slug. Example: my-project
State
state
optionsOptionalState. Options: Open, Merged, Declined, Superseded
Sample request
{
  "workspace": "e.g. my-team",
  "repo_slug": "e.g. my-project",
  "state": "{{trigger.state}}"
}
Returns
{
  "size": 5,
  "values": [
    {
      "id": 42,
      "state": "OPEN",
      "title": "Fix login"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Pull Requests.

Any of these apps can fire this action as part of a workflow.

Gmail → Bitbucket
1 Gmail triggers
Slack → Bitbucket
13 Slack triggers
Google Sheets → Bitbucket
2 Google Sheets triggers
HubSpot → Bitbucket
18 HubSpot triggers
FAQ

Questions about List Pull Requests.

What does the List Pull Requests action do in Bitbucket?
Returns paginated PRs with filter by state (OPEN, MERGED, DECLINED, SUPERSEDED), source/destination branch, author. The base query for "PRs awaiting review" daily nudges or for code-review velocity reporting.
What inputs does List Pull Requests require?
Required: Workspace, Repository Slug. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Bitbucket returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Pull Requests support batch operations?
Yes. Run List Pull Requests inside a Loop node to process arrays. TinyCommand handles Bitbucket's rate limits automatically so you don't have to throttle manually.
More actions

Other Bitbucket actions.

Action
Add PR Comment
Posts a comment on a pull request. Useful for AI-driven code-review bots, for cross-tool notifications ("Linear issue X closed → comment on the linked PR"), or for automated linting/style feedback.
Action
Create Issue
Files a new issue in a Bitbucket repository with title, content, kind (bug/enhancement/task), priority, assignee. For "Sentry error → file a Bitbucket issue" or "support ticket marked as bug → file repo issue" workflows.
Action
Create Pull Request
Opens a new PR from source branch to destination branch with title, description, and reviewers. Useful for automation that auto-creates PRs from generated branches (e.g., dependabot-style auto-update workflows).
Action
Get Pull Request
Returns the PR by ID with all metadata — branches, reviewers, status, merge conflicts, build status. The standard lookup for cross-tool sync workflows that need current PR state.
Action
Get Repository
Returns the repository with name, description, language, visibility, fork info, recent activity. Useful for "show me all repos this team owns" inventory workflows or for validating a repo exists before downstream operations.
Action
List Branches
Returns the repository's branches with last commit info. Useful for "find branches that haven't been touched in 90+ days for cleanup" maintenance workflows.