Bitbucket

Send Bitbucket Cloud repository events to Telegram.

Add the webhook

In your repository open Repository settings → Webhooks → Add webhook and fill the form:

Field Value
Title Any name, for example Thook
URL https://thook.altr.dev/hooks/bitbucket/{unique_path}
Secret The secret key from the bot
Status Active
Triggers Choose from a full list of triggers, then pick the ones below

Bitbucket does not show the secret again after you save the webhook. Save, then open the webhook and use View requests: a 202 means it works.

Supported events

  • Push, including the creation and the deletion of branches and tags
  • Fork
  • Build status created and build status updated: the result of Bitbucket Pipelines and of the other CI tools that report on a commit
  • Pull requests: created, updated, approved, approval removed, changes requested, change request removed, merged, declined, and comments (created, updated, deleted)
  • Issues: created, updated and comment created, when the issue tracker is on

You choose the events: Thook shows the ones the webhook sends. Other events are accepted and ignored.

What you get

The title tells the event, then the details, who did it and a link to the event as the last line. The meaning of the icons is in the quick start.

📣 Push · Bitbucket

📦 workspace/app · main
📔 2 commits
• Fix the start message
• Add tests

👤 Alice

View push
🟢 Build passed · Bitbucket

📦 workspace/app
📔 709d658
⚙️ Unit Tests · 🕒 1m 5s

👤 Alice

View build
🟣 Pull request merged · Bitbucket

📦 workspace/app
📰 #7 Add rate limiting
🌿 feat/rate-limit → main

👤 Bob

Open PR

A few things are different from the other services:

  • Bitbucket lists up to 5 commits of a push and does not say how many there are in total: when there are more the message says 5+ commits.
  • The status of a build is not tied to a branch, the message shows the commit instead.
  • A build is one message that updates from running to the result, and the result is a new message: see Workflows, pipelines and deploys.

Troubleshooting

  • 401 in View requests: the Secret is different from the one in the bot message. Bitbucket does not show it after saving, so edit the webhook and type it again.
  • Nothing arrives but the status is 202: the event is not in the list above.
  • Redeliver: Bitbucket keeps the requests of the last days in View requests, with the option to send them again.