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
  • Jamie Talbot commented
    February 09, 2018 16:59

    Notifications are actually fundamentally broken for workflows in 2.0. A per-build notification-basis means the notification status is based on the success of the last run build step in a workflow, even if a previous build step failed. (Also noted here by others:

    This false sense of security is incredibly dangerous, and means the notifications cannot be relied upon, which makes them unfit for purpose.

    Accurate reporting of workflow pipelines should be table stakes, and I consider this a bug, not a feature.

  • Chris Portela commented
    February 16, 2018 17:08

    While I love CircleCI this issue has made me seriously consider and try out many alternatives when we were perfectly fine using CCI before.

    Part of our CI workflow is to ensure other developers on our team are aware of each other's actions and if there is a problem.

  • Steve Hollaar commented
    March 09, 2018 21:31

    The false-positive "fixed" slack notifications are our biggest pain point with CircleCI 2 (which has otherwise been great).

  • Cyril Duchon-Doris commented
    March 11, 2018 16:19

    In case this feature takes time to implement, maybe a "quick-win" would be to add a documentation section on how to make customized slack notifications eg in the likes of

  • Olaf Tomalka commented
    March 14, 2018 13:44

    What is more, the experimental ability to filter status reports by branch doesn't work anymore. Which means that failed PRs warn our sysops team unnecessarily.

  • cole morrison commented
    March 19, 2018 20:42

    Though it's nice to see that a notification has occurred, it's kind of pointless because we always wind up back in the console if we need anymore details.  At the very least, the name of the build step that's completed, in context of a workflow, should be shown.

  • Steve Tooke commented
    March 20, 2018 09:09

    It would be really useful to have a workflow level notification.

    I do value seeing the individual job statuses though. Maybe a combination could be managed with threads?


    Workflow test-and-deploy started for commit abc123
    -- Job: build pass
    -- Job: unit test passed
    -- Job: acceptance test failed
    -- Workflow test-and-deploy failed
  • Chris Vermilion commented
    March 22, 2018 15:20

    Yeah, per-job notifications took our channel from "noisy but useful to keep an eye on" to "completely unusable". Now instead of keeping an eye on a submitted job (maybe a PR that I'll merge if CI passes), I'll just check in on it later. This is fine if everything goes well, but when things start failing the cycle time gets long. I could build a custom notification system manually as in [this comment over in the discussion forum](, but I guess I'd assumed this would actually get fixed before it was worth devoting the energy...

  • Andy McVitty commented
    April 15, 2018 09:38

    Came here to suggest "the name of the build step that's completed, in context of a workflow, should be shown." in slack notifications.

    I see that many people are making use of workflows for more sophisticated pipelines than ours, and need notifications like "notify if any stage of the workflow failed". That is understandable, and we would also benefit from those more sophisticated notifications, but I think adding a little more info into the existing notifications could be a quick win. 


  • Toby Pinder commented
    April 26, 2018 16:40

    Strongly agree with this. We had to create our own solution as part of the Build process.

    A general revamp could also use the slack API's `chat.update` method to represent each workflow step as a distinct attachment with it's own blue/red/green colouring, with an emphasis on linking to the Workflow over individual build steps.

    This is similar to how github themselves handle things in the new Github slack integration - PRs end up having the `checks` flash up and update as the build is continuing.

  • 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.

  • 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??

  • Fedya Skitsko commented
    June 19, 2018 02:03

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

  • 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.

  • 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!

  • 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.

  • 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

  • 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.

  • Paul Mackay commented
    August 15, 2018 09:25

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

  • 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.

  • Admin
    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. 

  • 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. 

  • Admin
    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.

  • Guest commented
    October 05, 2018 00:04

    Please enable for raptor235 thank you

  • 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..

  • Admin
    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.

  • 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) ?

  • 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.

  • 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.

  • 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.