Revamped Slack notifications for Workflows (2.0)

Slack integration is really neat, yet with the introduction of workflows in 2.0, it creates a lot of spam because each job will create its own notification

It would be nice if either of the changes would be made:

  • Trigger a single notification containing 

- Name, status and link to each individual job of a given workflow
- Name of the workflow as well as a link to its workflow-run

  • If notifications must be per individual job, then notification content should include:

- Name of the job 
- Name of the workflow as well as a link to its workflow-run

  • Guest
  • Feb 2 2018
  • Shipped
  • Attach files
  • Nora Lin commented
    August 07, 2019 18:43

    +1, and would like more ability to customize slack notifications, specifically, including env vars that were passed in, and what branches to notify.

  • Michael Hoffman commented
    January 14, 2019 18:53

    +1 I'd really love to send notifications for certain branches and not others, e.g. master only.

  • Adam Anderson commented
    November 21, 2018 20:37

    Will live updates as described in be available soon? I'm only seeing notifications when a workflow is finished.

  • Gustavo Matias dos Santos commented
    November 21, 2018 19:37

    thanks, Kunal! 

    Is there a way to only get notifications for a particular branch (e.g. master) or status (e.g. fixed or failed) ?

  • Kunal Jain commented
    November 21, 2018 19:18

    We have rolled out workflow level slack notifications for all customers. As mentioned in the original idea we have added a name, status and link of workflow with a link to a failed job within that workflow.

  • Nico Po commented
    October 24, 2018 11:33

    Would be great if we can send a notification with embed button to unhold directly in slack step of type approval.

    Also, being able to deliver notification to a specific slack channel depending on branch, etc..

  • Guest commented
    October 05, 2018 00:04

    Please enable for raptor235 thank you

  • Kunal Jain commented
    October 04, 2018 22:25


    We are starting an early beta for slack notifications. If you are interested, please email your GitHub or Bitbucket organization name at and we can enable slack notifications from your organization.

    Thank you so much for your patience.

  • P BK commented
    September 12, 2018 21:48

    @Kunal Jain

    What is the status on this ? What does early Q4  mean ?

    You forced  all of us to move to 2.0 by August 31st and now essentially Slack notifications are unusable. 

  • Kunal Jain commented
    August 28, 2018 18:04

    We are working on revamping slack and email notifications for workflows. This feature should be available by early Q4. Thank you so much for your patience. 

  • Stefan Wallin commented
    August 28, 2018 07:24

    I've submitted a support request. That ticket requests an update on the time horizon for this feature. Will get back to you with their responses.

  • Paul Mackay commented
    August 15, 2018 09:25

    Any update on when this feature might make it to release? 

  • Anthony Drogon commented
    August 09, 2018 16:04

    If it's also about never replying, you could have kept this "ideas" section in the Discuss forum.

    The current Slack integration is a shame, it can't be that hard to send one message instead of N.

  • David Lewis-Crosby commented
    August 03, 2018 09:08

    I like the fact that it says this is planned, but could there be an indication of a likely implementation date? It would allow us to evaluate the worth of implementing our own workaround

  • Jon Evans commented
    July 31, 2018 12:48

    Has there been any official response regarding this issue? I'm noticing it now during switching a pipeline over. Notifications are really noisy in their current state for workflows that involve more than a few jobs.

  • Gustavo Matias dos Santos commented
    July 24, 2018 16:01

    Does this also involves targeting specific branches? e.g. master only Slack notifications.

    If not, can anyone please point me to a doc for that?

    I'd love for my team to become more aware of master failures without getting spammed of not-so-important branches that have failed. thanks!

  • Joshua Wiens commented
    July 19, 2018 08:48

    So here is my issue with the existing implementation

    • The information is of little or no value
    • It's spams the channel on a real life workflow
    • The status returns false positives, zero value in that as well


    There is no denying the usefulness of workflows but we have also come to rely on the slack notifications as well, particularly off hours. As it stands right now, imo they tarnish what is an otherwise extremely powerful feature.


    There is an example of my smallest build in the attached screenshot, it's hard to find value in that information. Particularly when two of those steps actually failed.

  • Fedya Skitsko commented
    June 19, 2018 02:03

    That's crazy spam, I am disabling Slack integration. Could you please fix that?

  • Bob Myers commented
    June 09, 2018 05:18

    I hate people who just write "+1" without adding any value to the thread.


    But I will be one anyway. Is anyone looking at this bug? Is there any prognosis for fixing it? Sorry, I don't time time or bandwidth to replace these broken slack and email notifications with ones of my own. Why was this not a basic feature implemented as part of 2.0? Is anyone there? HELLO??

  • Geidivan Brito commented
    June 06, 2018 17:19

    Missing this feature. Also, the capability to set filter branch to not receive all branchs (nightly builds, development) notifications.

  • Load older comments