Short answer: You can list branches in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket List Branches action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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" |
{"workspace": "e.g. my-team","repo_slug": "e.g. my-project","q": "e.g. name ~ \"feature\"","sort": "e.g. -target.date","pagelen": "25"}
{"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.
Any of these apps can fire this action as part of a workflow.