List Pull Requests: Bitbucket action

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.

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. Tiny Command handles Bitbucket's rate limits automatically so you don't have to throttle manually.

More actions