Get Repository: 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

Sample request

{
  "workspace": "e.g. my-team",
  "repo_slug": "e.g. my-project"
}

Returns

{
  "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.

FAQ

Questions about Get Repository.

What does the Get Repository action do in Bitbucket?

Returns the repository with name, description, language, visibility, fork info, recent activity. Useful for "show me all repos this team owns" inventory workflows or for validating a repo exists before downstream operations.

What inputs does Get Repository 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 Get Repository support batch operations?

Yes. Run Get Repository 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