Notifications for Bitbucket Pipelines

Bitbucket Pipelines can send notifications to your team's chat room, and also to email.


Chat notifications


It's easy to get Pipelines to notify Hipchat rooms about build result successes and failures:

Read more about setting up notifications for Hipchat.


Pipelines can notify Slack about build result successes and failures. 

To configure Slack notifications:

  1. Install the Bitbucket integration in Slack.
  2. Copy the unique webhook URL from the Slack installation guide.
  3. Go to your Bitbucket repository > Settings > Webhooks.
  4. Add a webhook with the unique URL from the Slack installation guide. 
  5. Go to Triggers > Choose from a full list of triggers.
  6. Select:
    • Build status updated to get success and fail notifications
    • Build status created to get a notification when a pipeline is started
  7. 保存をクリックします。

Push a change to trigger a pipeline and view notifications in the Slack channel that you selected in the installation process:

Manual steps and notifications

Pipeline completion notifications are sent when there are no further steps that can be run in the pipeline. This means notifications are sent when:

  • the initial automated steps in the pipeline are complete, even if later manual steps remain to be run
  • when a manual step (and any following automated steps) completes, even if later manual steps remain to be run.

This is designed to cover the primary use case of manual steps being used for deployments, where the team should be notified about deployments.

Some notification channels (e.g. HipChat/Stride) allow filtering of build status, which can be used to further filter notifications from manual steps.



You can get emails about:

  • when you push and the pipeline fails.
  • all failed pipelines in a repository.

Personal notifications

If you provided your email in the Bitbucket settings for your account, you'll get notified each time your push triggers a pipeline that fails:

Currently, you can unsubscribe from personal notifications by following the steps in Enabling or disabling email.

Repository notifications

You can subscribe to notifications about all failed pipelines for a repository:

Note: If you clear the All pipelines checkbox for a repository, you will still continue to receive personal notifications.

Generic webhooks

You can set up notifications for services by creating webhooks, just like in the Slack example on this page (Steps 2 to 7). Pipelines uses the commit status API of Bitbucket Cloud.

You can add the following webhooks:

最終更新日 2017 年 11 月 8 日


Powered by Confluence and Scroll Viewport.