Atlassian Bitbucket Cloud
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.
Connect Atlassian Bitbucket Cloud to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
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.
Configuration
| Option | Description |
|---|---|
WorkspaceType: text Required: True | Your workspace ID — the part after |
Authentication typeType: select Required: True |
Linking Atlassian Bitbucket Cloud to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Atlassian Bitbucket Cloud
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
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 | — | — |