List Repositories: 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
Role Filter role	options	Optional	Role Filter. Options: All, Owner, Admin, Contributor, Member
Page Size pagelen	string	Optional	Page Size. e.g. "25"

Sample request

{
  "workspace": "e.g. my-team",
  "role": "{{trigger.role}}",
  "pagelen": "25"
}

Returns

{
  "size": 42,
  "values": [
    {
      "slug": "my-project",
      "full_name": "team/my-project",
      "is_private": true
    }
  ]
}

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

FAQ

Questions about List Repositories.

What does the List Repositories action do in Bitbucket?

Returns paginated repos in the workspace with name, slug, language, visibility. Useful for inventorying team repos and for "iterate over every repo" cross-repo automation patterns.

What inputs does List Repositories require?

Required: Workspace. 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 Repositories support batch operations?

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