Feature Marketplace · Connectors

Bitbucket Connector

Atlassian Bitbucket Cloud Git hosting platform. Syncs repositories, pull requests, commits, and pipeline runs via the Bitbucket Cloud REST API 2.0 with HMAC-signed webhook support.

Connectors connector devops

What syncs

The Bitbucket records STRAX brings into your hub.

Each kind of record is mapped once to your company model in the STRAX hub, then kept current in every system that needs it. Where Bitbucket announces changes, they arrive as they happen.

Repositories

Repositories in the workspace including visibility, language, size, and main branch details.

Changes arrive as they happen

Pull Requests

Pull requests for the repository including state, draft flag, branches, and review counters.

Changes arrive as they happen

Commits

Commit history for the repository including author, message, and parent links.

Changes arrive as they happen

Pipelines

Bitbucket Pipelines runs including state, result, trigger target, and timing.

Bitbucket data in your own SQL Server, then wherever it is needed.

STRAX is a self-hosted integration platform. The Bitbucket records land in the STRAX hub, a SQL Server database on your own servers, where your reports, portals and workflows read them. From there the hub delivers them to the other systems you connect, whether those run on SQL Server, MySQL, PostgreSQL or another API. STRAX signs in to Bitbucket with an API key that you provide, stored encrypted.

About this listing

Version1.0.1
AuthorSTRAX
CategoryConnectors
Published2026-07-15

What's inside

Connector profile 1

Free listing

Install it from Feature Marketplace inside STRAX

Open Feature Marketplace

In your STRAX installation, open Feature Marketplace from the navigation.

Find "Bitbucket Connector"

Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.

Install

Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.

Back to the catalogue →

See it on your own systems.

A demo takes an hour, on your data landscape rather than ours.