Short answer: You can list commits in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket List Commits action to a workflow, map its 4 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 |
Branch branch | string | Optional | Branch or tag name to list commits from |
Page Size pagelen | string | Optional | Page Size. e.g. "30" |
{"workspace": "e.g. my-team","repo_slug": "e.g. my-project","branch": "e.g. main","pagelen": "30"}
{"values": [{"date": "2025-01-15T12:00:00+00:00","hash": "abc123def456","links": {"html": {"href": "https://bitbucket.org/my-team/my-project/commits/abc123def456"}},"author": {"raw": "John Doe <john@example.com>"},"message": "Fix login redirect on Safari"}]}
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.
