For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/integrations/bitbucket.md.
Docs

Bitbucket integration

The Bitbucket integration connects your Bitbucket workspace to Flezise so the builder agent can read source code and open pull requests when a run finishes.

The Bitbucket integration detail page showing Connected status, the Inbound events card, and the Link repository button

Connect

Open Project Settings → Integrations → Bitbucket. Click Connect to authorize via OAuth, or Connect with token to enter an app password directly.

OAuth requests these scopes: repository and pullrequest. The repository scope covers read access; pullrequest allows the integration to open pull requests. Bitbucket OAuth uses basic auth token exchange and supports token refresh.

Token connect accepts three credential fields:

FieldWhat to enter
WorkspaceYour Bitbucket workspace slug, for example my-workspace
UsernameYour Bitbucket account username
App PasswordAn app password generated under Personal settings → App passwords

The app password needs the Repositories: Read and Pull requests: Write permissions.

Once connected, copy the Webhook URL from the connection panel and register it in the repository under Repository settings → Webhooks. Paste the Signing Secret from the same panel into the Secret field.

Capabilities

CapabilityWhat it means
WebhooksReceives and verifies inbound events from Bitbucket
Source PullProvides an authenticated clone URL for the linked repository
PR CreateOpens a pull request via the Bitbucket API when a run completes

Bitbucket does not support the Reply capability. The builder agent does not post comments back to Bitbucket issues or pull requests.

Configuration

After connecting, link a repository so the builder agent knows where to clone and push. Press Link repository on the detail page and enter the repository in workspace/repo format.

The optional Repository config field sets a default repository for automation. When set, the builder agent targets that repository without requiring an explicit choice for each run.

Events

Bitbucket sends two event types that Flezise receives:

EventWhat triggers itAction
pullrequest:createdA pull request is openedAddress the review (address_review)
repo:pushA commit is pushed to the repositoryReceived and verified; no work item created

Only pullrequest:created produces an intent and can start agent work. The repo:push event is received and signature-verified but does not map to an action, so no work item appears.

Flezise deduplicates deliveries using the x-request-uuid header. Bitbucket signs each delivery with HMAC-SHA256 in the x-hub-signature header.

The Inbound events card on the detail page controls whether events from this connection can start agent work. Toggle Allow work-item triggers on to enable event-driven work items for pull request events.

FAQ

Pushes arrive but no work items appear. Is that expected?

Yes. The repo:push event is verified and recorded but has no mapped action. Only pullrequest:created creates work items through the Address review path.

The webhook shows a 401 response.

The signing secret does not match. Copy the Signing Secret from the Flezise connection panel and paste it into the Secret field on the Bitbucket webhook form.

Next steps