Your customers connect their Bitbucket Cloud workspace once and Askel takes it from there. Pull requests, pipeline runs, repository events, and commit metadata flow into your product without your team writing a single line of webhook plumbing. Askel handles Basic auth, token storage, and header composition so your codebase stays clean.
Trigger workflows when a PR is opened, marked as ready, approved, declined, or merged. Filter by target branch, reviewer, or repository so only the events your product needs actually land in your ingest endpoint.
Subscribe to pipeline step completions and surface pass or fail status in your product alongside the commit SHA and branch that triggered the build. Useful for release gates and deployment dashboards.
Pull open issues from any authorized repository, update their status, assign them, or add comments. Mark issues as resolved once your product has processed them to keep the two systems in sync.
Read branch names, latest commit SHAs, and commit messages for the repositories in scope. Lets your product link its own records to the exact commit that produced them.
Askel registers the Bitbucket webhook on the customer's workspace at connect time and removes it on disconnect. Your team never has to ask a customer to set up a webhook manually.
Customers can authorize a single repo, a handful of repos, or the entire workspace. Askel enforces that boundary and will not request data from repositories outside the agreed scope.
You sell release-management software. A customer, Harborview Labs, runs three microservices in a workspace called harborview. Their release process requires that every open pull request targeting the release/2.5 branch be merged or declined before the weekly deployment window opens. Today that check is a manual Slack message and a spreadsheet.
Harborview's admin clicks Connect Bitbucket inside your product. They paste their Atlassian email and an API token scoped to the harborview workspace. Askel composes the Basic auth header and verifies the credentials against https://api.bitbucket.org/2.0/user before storing them.
In your product's onboarding wizard, a Harborview admin sets the workspace to harborview, the repository to harborview/platform, and the target branch filter to release/2.5. Askel registers the pullrequest webhook on the repo automatically.
Each time a PR targeting release/2.5 is opened, updated, approved, or merged, Askel forwards a structured event to your product's ingest endpoint with the PR title, author, reviewers, approval count, and current state.
Your product queries the current open PRs for release/2.5, finds the two PRs that are still awaiting approval, and surfaces them in the release dashboard with direct Bitbucket links and reviewer names.
Once the last open PR is merged, Askel sends the pullrequest:fulfilled event, your product marks the release/2.5 gate as green, and the release lead gets a notification that the deployment window can open.
Customer's Bitbucket admin generates a scoped API token at id.atlassian.com/manage-profile/security/api-tokens and pastes it into Askel along with the admin's Atlassian email. Askel composes the Basic auth header at request time; the token never reaches your servers.
© 2025 Askel.ai. All rights reserved.