Engineering integration guide
Bitbucket + UbiGrowth workflows
Bitbucket is Atlassian's source control platform, holding repositories and pull request workflow. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Bitbucket part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around Bitbucket with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Repository, Pull Request, Commit, Pipeline, Workspace, and Branch Restriction. Bitbucket scopes repositories to a Workspace, and Bitbucket Cloud and Bitbucket Data Center have different APIs with different authentication. A workspace slug is not portable between them.
Bitbucket is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Launch is the usual destination for this connection, because the value shows up as a tool, dashboard, or internal surface built on the connected data.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. Bitbucket knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a Bitbucket integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Bitbucket's.
Identity and matching
Bitbucket scopes repositories to a Workspace, and Bitbucket Cloud and Bitbucket Data Center have different APIs with different authentication. A workspace slug is not portable between them.
Start here
Read open Pull Requests blocked by a failing Pipeline and route them with the failing step named.
What this will not do
It will not behave like the GitHub API. The object names look similar and the semantics differ; port the design rather than the code.
The constraint to plan around
Branch Restrictions are enforced server-side, so automation cannot merge a PR that a restriction blocks even with repository write access — the restriction is the point.
Build notes
What you actually have to reason about in Bitbucket.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| workspace slug | the account boundary, and part of every path in Bitbucket Cloud |
| state | OPEN, MERGED, DECLINED, or SUPERSEDED — four states rather than open and closed |
| participants / approvals | approval is a participant attribute rather than a separate review object |
| source.commit.hash | what pipelines attach to |
| branch restrictions | server-enforced merge conditions that automation cannot bypass |
Authentication
App passwords or workspace access tokens for Cloud; Data Center uses a different API and different tokens entirely. Code written for one does not run against the other despite similar object names.
Events and delivery
Webhooks per repository or workspace cover pull request and pipeline events, delivered with retry. Payload shapes differ between Cloud and Data Center.
Workflow
How the Bitbucket workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
Bitbucket is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the Bitbucket workflow is allowed to write anything.
Step 01
Separate read from act
Reading Bitbucket for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the Bitbucket workflow.
- 01
Start read-only against Bitbucket and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
Once pipeline-blocked PRs are routed, add branch-restriction visibility so contributors know why a merge is blocked without asking.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a Bitbucket integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Code written for Cloud fails against Data Center.
Cause
They are different APIs with different authentication.
Fix
Treat them as separate integrations rather than one with a flag.
Symptom 02
A merge attempt is rejected despite write access.
Cause
A branch restriction is enforced server-side.
Fix
Read branch restrictions and surface them as the reason rather than retrying.
Symptom 03
PR state logic misbehaves on some pull requests.
Cause
SUPERSEDED and DECLINED were treated as a single closed state.
Fix
Handle all four states explicitly.
What changes at scale
Rate limits are per user or per app, per hour. Workspace-wide sweeps should be incremental against updated timestamps rather than full enumeration.
Examples
What a working Bitbucket workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Repository workflows
With Bitbucket connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading Bitbucket gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- Branch Restrictions are enforced server-side, so automation cannot merge a PR that a restriction blocks even with repository write access — the restriction is the point.
- Merging through the API bypasses whatever local review convention exists, even where restrictions permit it. Automation with merge rights should be narrow and auditable.
- When porting a GitHub integration directly. The object names align, the semantics do not, and assuming otherwise produces subtle state errors.
- Write or action access to Bitbucket is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
Bitbucket integration questions.
What records does a Bitbucket integration actually work with?
The primary records are Repository, Pull Request, Commit, Pipeline, Workspace, and Branch Restriction. Bitbucket scopes repositories to a Workspace, and Bitbucket Cloud and Bitbucket Data Center have different APIs with different authentication. A workspace slug is not portable between them.
What should the first Bitbucket workflow be?
Read open Pull Requests blocked by a failing Pipeline and route them with the failing step named.
What will a Bitbucket integration not do?
It will not behave like the GitHub API. The object names look similar and the semantics differ; port the design rather than the code.
What is the main constraint to plan around?
Branch Restrictions are enforced server-side, so automation cannot merge a PR that a restriction blocks even with repository write access — the restriction is the point.
What changes about a Bitbucket integration at scale?
Rate limits are per user or per app, per hour. Workspace-wide sweeps should be incremental against updated timestamps rather than full enumeration.
How does authentication work for Bitbucket?
App passwords or workspace access tokens for Cloud; Data Center uses a different API and different tokens entirely. Code written for one does not run against the other despite similar object names.
Does Bitbucket support webhooks, and can they be trusted?
Webhooks per repository or workspace cover pull request and pipeline events, delivered with retry. Payload shapes differ between Cloud and Data Center.
What is the risk of writing to Bitbucket?
Merging through the API bypasses whatever local review convention exists, even where restrictions permit it. Automation with merge rights should be narrow and auditable.
When is connecting Bitbucket the wrong call?
When porting a GitHub integration directly. The object names align, the semantics do not, and assuming otherwise produces subtle state errors.
What should a Bitbucket integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Bitbucket to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on Bitbucket, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from Bitbucket — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in Bitbucket, and who decides.
Connecting Bitbucket is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.