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 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 INPROGRESS: Pipeline #42 for main Build Pipeline #42 for main is INPROGRESS in team/repo	⚙️ Build INPROGRESS: Pipeline #42 for main Build Pipeline #42 for main is INPROGRESS in team/repo
Build status updated `repo:commit_status_updated` ⚙️ Build FAILED: Pipeline #42 for main Build Pipeline #42 for main is FAILED in team/repo	⚙️ Build FAILED: Pipeline #42 for main Build Pipeline #42 for main 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
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

How to connect Bitbucket

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, open Repository settings and select Webhooks (under Workflow).
Click Add webhook.
Enter a Title (e.g. “Hookfire”).
Paste your Hookfire webhook URL into the URL field.
In the Secret field, click Generate secret (or type your own) and copy it. Bitbucket can’t show it again once the webhook is saved.
Under Triggers, select the events you want or choose Choose from a full list of triggers.
Click Save.

Step 3: Paste the Secret in Hookfire (recommended)

Go back to your Hookfire integration page and paste the secret into the Signing Secret field. Bitbucket signs every delivery with it in the X-Hub-Signature header, and Hookfire will reject any request it didn’t sign.

Step 4: Subscribe to Events

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

Step 5: 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