How to Set Up Bitbucket Webhook Notifications with Webhookify

Bitbucket is Atlassian's Git-based source code hosting and collaboration platform used by millions of developers and teams worldwide. Whether you use Bitbucket Cloud or Bitbucket Data Center, webhooks provide a powerful way to integrate your repository events with external services. Every push, pull request, build status update, or issue change can trigger an HTTP POST to a URL of your choice. With Webhookify, you can route those Bitbucket webhook events to Telegram, Discord, Slack, Email, or mobile push notifications, giving you real-time visibility into your repository activity without constantly refreshing the Bitbucket dashboard.

This guide covers the complete process of setting up Bitbucket webhooks with Webhookify, so your team stays informed about code changes, pull request activity, and CI/CD pipeline status in real time.

Why Monitor Bitbucket Webhooks with Webhookify?

• Real-Time Code Push Notifications: Know the moment someone pushes code to your repository. Get a Telegram or Slack message with the commit author, branch name, and commit message so you can stay on top of code changes across your team.

• Pull Request Workflow Alerts: Track the entire pull request lifecycle -- creation, approvals, merges, and rejections -- from your phone or chat app. Never miss a PR waiting for your review or a PR that was merged while you were away.

• CI/CD Build Status Tracking: Bitbucket sends commit status webhooks when your CI/CD pipeline (Bitbucket Pipelines, Jenkins, or any other CI tool) updates the build status. Get instant alerts when builds pass or fail without watching the pipeline dashboard.

• AI-Powered Commit Summaries: Raw Bitbucket webhook payloads include repository metadata, commit hashes, author information, and branch references. Webhookify's AI summarizes this into clear messages like "John pushed 3 commits to feature/auth-flow on myapp repo" for quick comprehension.

• Multi-Repository Monitoring: If you manage multiple Bitbucket repositories, you can point all of their webhooks to a single Webhookify endpoint. All events are logged centrally, and notifications include the repository name so you can distinguish between projects.

Prerequisites

1. A Bitbucket Cloud or Bitbucket Data Center account. Sign up at bitbucket.org if you do not have one.
2. Admin access to the repository you want to monitor (needed to configure webhooks).
3. A Webhookify account. Sign up for free at webhookify.app.
4. A notification channel configured in Webhookify (Telegram bot, Discord webhook, Slack workspace, or Email address).
5. At least one repository with code pushes or pull request activity.

Step-by-Step Setup Guide

https://hook.webhookify.app/w/your-unique-endpoint-id

Bitbucket Webhook Events You Can Monitor

Full reference of Bitbucket Cloud webhook triggers:

Repository:

• repo:push -- One or more commits pushed to the repository
• repo:fork -- Repository forked
• repo:updated -- Repository settings updated
• repo:transfer -- Repository transferred to a different owner
• repo:commit_comment_created -- Comment added to a commit
• repo:commit_status_created -- Build status created for a commit
• repo:commit_status_updated -- Build status updated for a commit

Pull Requests:

• pullrequest:created -- New pull request opened
• pullrequest:updated -- Pull request updated (new commits, description change)
• pullrequest:approved -- Pull request approved by reviewer
• pullrequest:unapproved -- Approval removed from pull request
• pullrequest:fulfilled -- Pull request merged
• pullrequest:rejected -- Pull request declined
• pullrequest:comment_created -- Comment added to pull request
• pullrequest:comment_updated -- Pull request comment edited
• pullrequest:comment_deleted -- Pull request comment removed

Issues:

• issue:created -- New issue created
• issue:updated -- Issue modified
• issue:comment_created -- Comment added to issue

Each webhook payload includes the actor (who triggered the event), the repository details, and the specific resource data (commit info, PR details, or issue content).

Real-World Use Cases

• Code Review Workflow: Route pullrequest:created events to a Slack channel so your team knows the moment a new PR needs review. Follow up with pullrequest:approved and pullrequest:fulfilled alerts to track the review and merge process without checking Bitbucket.

• CI/CD Pipeline Monitoring: Monitor repo:commit_status_updated events to track your build pipeline status. Get instant Discord or Telegram alerts when a build fails so developers can fix it immediately, reducing the feedback loop for broken builds.

• Main Branch Protection: Set up a webhook that monitors repo:push events and get a push notification every time someone pushes directly to the main branch. This helps enforce branching policies and catch accidental direct pushes.

• Open-Source Project Activity: Forward all repository events to a Discord channel for your open-source community. Contributors can see new issues, pull requests, and commits in real time, fostering collaboration and transparency.

Example Notification

When code is pushed to a Bitbucket repository, Webhookify delivers a notification like this:

{
  "push": {
    "changes": [
      {
        "new": {
          "name": "main",
          "type": "branch",
          "target": {
            "hash": "a1b2c3d4e5f6",
            "message": "Fix authentication middleware and add rate limiting",
            "author": {
              "raw": "Sarah Chen <sarah@company.com>"
            },
            "date": "2026-02-21T11:45:00+00:00"
          }
        },
        "commits": [
          {
            "hash": "a1b2c3d4e5f6",
            "message": "Fix authentication middleware and add rate limiting",
            "author": {
              "raw": "Sarah Chen <sarah@company.com>"
            }
          }
        ]
      }
    ]
  },
  "actor": {
    "display_name": "Sarah Chen",
    "nickname": "sarahchen"
  },
  "repository": {
    "full_name": "company/backend-api",
    "name": "backend-api"
  }
}

Webhookify's AI summary would display:

Bitbucket Push: Sarah Chen pushed 1 commit to main on company/backend-api: "Fix authentication middleware and add rate limiting"

This concise format lets you quickly understand who pushed what and where.

Troubleshooting

1. Webhook not triggering on push events: Make sure the webhook status is set to Active in Bitbucket's webhook settings. Also verify the trigger is set to at least repo:push. If you chose "Choose from a full list of triggers" but did not check any boxes, no events will be sent.

2. Receiving push events but not pull request events: Pull request events require separate trigger selections. Go back to your webhook settings in Bitbucket and expand the full trigger list. Check the pullrequest:created, pullrequest:fulfilled, and other PR triggers you need.

3. Build status events are not appearing: Build status webhooks (repo:commit_status_created and repo:commit_status_updated) require that your CI/CD tool (Bitbucket Pipelines, Jenkins, etc.) is correctly configured to report build statuses to Bitbucket. If your pipeline does not report statuses, these webhooks will not fire.

4. Webhook shows a "Last triggered" date but no notification in Webhookify: Check if the Webhookify URL is correctly pasted with no extra spaces or characters. Also verify your Webhookify notification channel is properly connected by sending a test notification from the Webhookify dashboard.

5. Too many notifications from a busy repository: If your repository receives dozens of pushes per day, you might get overwhelmed. Consider creating separate webhooks for critical events (like pushes to main or PR merges) and lower-priority events (like PR comments). Route critical events to mobile push and lower-priority events to a Slack channel.

Related Articles

• Webhook Security Best Practices
• How to Get Webhook Alerts on Discord
• CI/CD Deployment Notifications with Webhooks
• Developer Workflow Automation with Webhooks
• How to Set Up GitHub Webhook Notifications
• How to Set Up GitLab Webhook Notifications