ActionBitbucketUpdated June 2026

What branches exist in this Bitbucket repo?

Short answer: Drop the "Bitbucket → List Branches" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 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.

Field	Type	Required	Description
Workspace workspace	string	Required	Workspace. Example: my-team
Repository Slug repo_slug	string	Required	Repository Slug. Example: my-project
Query Filter q	string	Optional	Bitbucket query filter expression
Sort sort	string	Optional	Field to sort by (prefix with - for descending)
Page Size pagelen	string	Optional	Page Size. e.g. "25"

Sample request

{
  "workspace": "e.g. my-team",
  "repo_slug": "e.g. my-project",
  "q": "e.g. name ~ \"feature\"",
  "sort": "e.g. -target.date",
  "pagelen": "25"
}

Returns

{
  "size": 5,
  "values": [
    {
      "name": "main",
      "links": {
        "html": {
          "href": "https://bitbucket.org/my-team/my-project/branch/main"
        }
      },
      "target": {
        "date": "2025-01-15T12:00:00+00:00",
        "hash": "abc123def456"
      }
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Branches.

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 Branches.

What does the List Branches action do in Bitbucket?

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.

What inputs does List Branches 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 Branches support batch operations?

Yes. Run List Branches 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