Linking Atlassian Bitbucket Cloud as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Atlassian Bitbucket Cloud connector syncs repositories, pull requests, commits, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Connect your Bitbucket Cloud workspace to sync repositories, pull requests, commits, pipelines, and more.
Your credentials need the repository, pullrequest, pipeline, project, and account read scopes. Avoid app passwords - Atlassian is retiring them; use an API token or an access token instead.
You'll be asked for:
- Workspace: your workspace ID — the part after
bitbucket.org/in your workspace URL. - Authentication type: choose between Atlassian API token and Access token.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Atlassian Bitbucket Cloud tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
WorkspaceType: text Required: True | Your workspace ID — the part after |
Authentication typeType: select Required: True |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
repositories | A git repository in the Bitbucket Cloud workspace. | Incremental, Full refresh | updated_on, created_on | — |
pull_requests | A pull request in any repository of the workspace, in any state (open, merged, declined, or superseded). | Incremental, Full refresh | updated_on, created_on | — |
commits | A commit reachable from any branch of any repository in the workspace, newest-first in topological order. | Incremental, Full refresh | date | — |
pipelines | A Bitbucket Pipelines run (CI/CD build) in any repository of the workspace. | Incremental, Full refresh | created_on | — |
deployments | A deployment of a pipeline release to an environment, in any repository of the workspace. | Full refresh | — | — |
pull_request_activity | An entry in the activity log of a pull request: a review comment, an update to the pull request, an approval, or a request for changes. | Incremental, Full refresh | activity_date | — |
pull_request_comments | A comment on a pull request, including global comments, inline comments on a file or line of code, and replies. | Incremental, Full refresh | updated_on, created_on | — |
pipeline_steps | A single step of a Bitbucket Pipelines run, with its own state and timings. Pipelines record only the run as a whole, so this is where per-step CI duration and outcome live. | Incremental, Full refresh | pipeline_created_on | — |
commit_statuses | An external build or check result reported against a commit, such as a CI job posting success or failure. Each status is addressed by its commit and key. | Incremental, Full refresh | commit_date | — |
branches | A branch in a repository. Pull requests, pipelines and deployments refer to branches by name. | Full refresh | — | — |
environments | A deployment environment configured on a repository. Deployments refer to these environments. | Full refresh | — | — |
projects | A project in the workspace. Projects group repositories under a project key. | Incremental, Full refresh | updated_on, created_on | — |
workspace_members | A user's membership in the Bitbucket Cloud workspace. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.