Email service management

With this service, you can set up Bitbucket Cloud to send an email message to a given email address, for each pushed changegroup. To send multiple emails, provide a comma-separated list of addresses, for example:,

Format of the Email Messages

Email messages are sent from

When a changegroup contains only one changeset, the email subject line will be of the following form:

Subject: commit/<project>: <user>: <commit msg>

When a changegroup contains two or more changesets, the email subject line will be of the following form:

Subject: commit/<project>: <x> new changesets

Setting Up the service

 You must have administrative access on a repository to add this service.

  1. Go to the repository's settings.
  2. Click Services in the left-hand navigation.
    The Services page appears.
  3. Select the Email service from the services dropdown.
  4. Click Add service.
    A new section appears for the Email service.
  5. Enter the following information:

    Email Enter the email address where Bitbucket should send the email messages.
  6. Press Save.

If you are having trouble with the service, see Troubleshoot Bitbucket Cloud services.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

12 Archived comments

  1. User avatar


    Is there a way to leave repo push e-mail subscriptions in the hands of the individual user instead of the admin?  I admin a Mercurial repo and would prefer to have the repo users take care of whether or not they want to receive push e-mails.


    02 Sep 2012
    1. User avatar


      A very simple way to do that would be to send the push e-mails to a mailing-list. Users could then subscribe to the mailing-list if they want to.


      24 Sep 2012
  2. User avatar


    I send all commits to a commits mailing list. If someone sees an interesting commit and uses the neat commenting features you have on the website, those comments are hidden from the people who follow the mailing list.

    I would like a feature where I can specify which project mailing list commit comments should be sent to.

    11 Oct 2012
    1. User avatar


      Hi. Please go ahead request this as an enhancement.

      11 Oct 2012
  3. User avatar


    Does this work for git commits as well as mercurial? We have not been successful in getting this to work for a git repo.

    22 Jan 2013
    1. User avatar


      It should.  If you are having problems getting it to work, please send an email to

      22 Jan 2013
  4. User avatar


    You need to get emails setup like Fisheye.. They were 1000X better

    20 Mar 2013
  5. User avatar


    Is there a way to configure email notifications to be received only for particular branch commits?

    15 May 2013
    1. User avatar


      Not right now.   You can request this as an enhancement.

      15 May 2013
  6. User avatar


    Thanks for this hook. if you get a moment please

    Warm regards

    24 Sep 2013
  7. User avatar

    Jan Sondergaard

    I just contacted Atlassian Support to hear how we can get email setup like we had it in FishEye. Those emails made us very productive and gave us good insight to what changed, with URLs to the diff. Seems like we have moved 30 years back in time with Bit Bucket emails, but perhaps we just don't know how to configure properly.

    10 Oct 2013
  8. User avatar

    Денис Минич

     Is it possible to send mails from the author email push or pullrequest.

    15 May 2015
Powered by Confluence and Scroll Viewport