ActionBitbucketUpdated September 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.

List Pull Requests in Bitbucket — start free All 10 Bitbucket actions

List Pull Requests in Bitbucket — start free

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Workspace workspace	string	Required	Workspace. Example: my-team
Repository Slug repo_slug	string	Required	Repository Slug. Example: my-project
State state	options	Optional	State. 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.

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 run history shows the failed step with its input and the error message Bitbucket returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Pull Requests support batch operations?

Run List Pull Requests inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Bitbucket's rate limits.

More actions