Bitbucket

Manage repositories, pull requests, and pipelines on Bitbucket Cloud.

Detail	Value
Category	Dev Tools
Base URL	https://api.bitbucket.org/2.0
Authentication	Bearer Token
Endpoints	5
Connector key	bitbucket

Using Bitbucket in a workflow

1. Go to Connections and click New Connection.
2. Pick Bitbucket from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /repositories/{workspace}	List repositories in a workspace
GET /repositories/{workspace}/{repo_slug}	Get a repository
GET /repositories/{workspace}/{repo_slug}/pullrequests	List pull requests
GET /repositories/{workspace}/{repo_slug}/pipelines	List pipelines
GET /repositories/{workspace}/{repo_slug}/commits	List commits

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /repositories/{workspace}

List repositories in a workspace

Detail	Value
Operation ID	scm.listRepos
Method	GET
Path	/repositories/{workspace}

Parameters

Name	Location	Type	Required
workspace	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bitbucket connection from the Connection dropdown.
3. In the Operation dropdown, select scm.listRepos.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bitbucket API reference.

GET /repositories/{workspace}/{repo_slug}

Get a repository

Detail	Value
Operation ID	scm.getRepo
Method	GET
Path	/repositories/{workspace}/{repo_slug}

Parameters

Name	Location	Type	Required
workspace	path	string	Yes
repo_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bitbucket connection from the Connection dropdown.
3. In the Operation dropdown, select scm.getRepo.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bitbucket API reference.

GET /repositories/{workspace}/{repo_slug}/pullrequests

List pull requests

Detail	Value
Operation ID	scm.listPRs
Method	GET
Path	/repositories/{workspace}/{repo_slug}/pullrequests

Parameters

Name	Location	Type	Required
workspace	path	string	Yes
repo_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bitbucket connection from the Connection dropdown.
3. In the Operation dropdown, select scm.listPRs.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bitbucket API reference.

GET /repositories/{workspace}/{repo_slug}/pipelines

List pipelines

Detail	Value
Operation ID	scm.listPipelines
Method	GET
Path	/repositories/{workspace}/{repo_slug}/pipelines

Parameters

Name	Location	Type	Required
workspace	path	string	Yes
repo_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bitbucket connection from the Connection dropdown.
3. In the Operation dropdown, select scm.listPipelines.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bitbucket API reference.

GET /repositories/{workspace}/{repo_slug}/commits

List commits

Detail	Value
Operation ID	scm.listCommits
Method	GET
Path	/repositories/{workspace}/{repo_slug}/commits

Parameters

Name	Location	Type	Required
workspace	path	string	Yes
repo_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Bitbucket connection from the Connection dropdown.
3. In the Operation dropdown, select scm.listCommits.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Bitbucket API reference.