Short answer: You can get repository in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket Get Repository action to a workflow, map its 2 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 |
{"workspace": "e.g. my-team","repo_slug": "e.g. my-project"}
{"slug": "my-project","links": {"html": {"href": "https://bitbucket.org/my-team/my-project"}},"language": "python","full_name": "my-team/my-project","is_private": true,"mainbranch": {"name": "main"},"description": "Our main project"}
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.
