Why use Hookfire with Bitbucket?

Instant push notifications

Get notified on your phone the moment a Bitbucket webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which Bitbucket events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how — push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in Bitbucket, and you're done. No code required.

Supported events

Event	Sample notification
Pull request created `pullrequest:created` 🔀 PR created: #3 Add feature X by testuser in team/repo	🔀 PR created: #3 Add feature X by testuser in team/repo
Pull request updated `pullrequest:updated` 📝 PR updated: #3 Add feature X by testuser in team/repo	📝 PR updated: #3 Add feature X by testuser in team/repo
Pull request merged `pullrequest:fulfilled` ✅ PR merged: #3 Add feature X merged by testuser in team/repo	✅ PR merged: #3 Add feature X merged by testuser in team/repo
Pull request declined `pullrequest:rejected` ❌ PR declined: #3 Add feature X declined by testuser in team/repo	❌ PR declined: #3 Add feature X declined by testuser in team/repo
Pull request comment `pullrequest:comment_created` 💬 Comment on PR #3 reviewer commented on Add feature X: Looks good, just one minor suggestion on line 42.	💬 Comment on PR #3 reviewer commented on Add feature X: Looks good, just one minor suggestion on line 42.
Build status created `repo:commit_status_created` ⚙️ Build SUCCESSFUL: CI Pipeline Build CI Pipeline is SUCCESSFUL in team/repo	⚙️ Build SUCCESSFUL: CI Pipeline Build CI Pipeline is SUCCESSFUL in team/repo
Build status updated `repo:commit_status_updated` ⚙️ Build FAILED: CI Pipeline Build CI Pipeline is FAILED in team/repo	⚙️ Build FAILED: CI Pipeline Build CI Pipeline is FAILED in team/repo
Issue created `issue:created` 🐛 Issue created: #8 Login page broken by testuser in team/repo	🐛 Issue created: #8 Login page broken by testuser in team/repo
Issue updated `issue:updated` 🐛 Issue updated: #8 Login page broken updated by testuser in team/repo	🐛 Issue updated: #8 Login page broken updated by testuser in team/repo
Issue comment `issue:comment_created` 💬 Comment on issue #8 testuser commented on Login page broken: I can reproduce this on Chrome 120.	💬 Comment on issue #8 testuser commented on Login page broken: I can reproduce this on Chrome 120.
Push `repo:push` 📦 Push to team/repo testuser pushed to team/repo: Fix navbar styling on mobile	📦 Push to team/repo testuser pushed to team/repo: Fix navbar styling on mobile

How to connect Bitbucket

Connecting Bitbucket to Hookfire

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select Bitbucket.
You’ll receive a unique Webhook URL — copy it.

Step 2: Add the Webhook in Bitbucket

In your Bitbucket repository, go to Repository settings → Webhooks.
Click Add webhook.
Enter a Title (e.g. “Hookfire”).
Paste your Hookfire webhook URL.
Under Triggers, select the events you want or choose Choose from a full list of triggers.
Click Save.

Step 3: Subscribe to Events

On your Hookfire integration page, toggle on the events you want to receive push notifications for.

Note: Bitbucket Cloud does not support webhook signing, so no signing secret is needed.

Step 4: Test

Click the Test button on your integration page, or push a commit to trigger a real event.

Supported Events

Event	Description
`repo:push`	Code was pushed
`pullrequest:created`	A pull request was created
`pullrequest:updated`	A pull request was updated
`pullrequest:fulfilled`	A pull request was merged
`pullrequest:rejected`	A pull request was declined
`pullrequest:comment_created`	A comment was added to a PR
`repo:commit_status_created`	A build status was created
`repo:commit_status_updated`	A build status was updated
`issue:created`	An issue was created
`issue:updated`	An issue was updated
`issue:comment_created`	A comment was added to an issue

Bitbucket