You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Jake - I can as I'm working with Trey as the Slack consumer. We utilize lots of SaaS products, and one way we do that is via a Slack Channel where we use a variety of methods to receive status updates. One of the methods is via Webhooks (others would be RSS and Twitter). I've noticed with Statuspage, the Webhooks you provide do not work with Slack - which is odd as I thought this was a standard. I've used your RSS feeds, and have noticed they are not nearly as quick as a webhook normally is.
Thanks @Craig Holland. I chatted with our product team about this and made sure a feature request was logged for this. This has come up a couple times in the past, and I definitely agree it would be useful.
Your use case fits that of what I think a lot of people would like to use Statuspage for - easily consuming the status of a variety of service providers in a single place. It's possible you'll see some solutions around this in the future.
In the short term, without knowing full details on the amount of effort this would take, I'll do my best to champion this (slack endpoint suppport for webhooks) through the finish line.
Hi @swift - thanks for checking in on this. This hasn't been added to the roadmap yet but there is a work-around you can use for getting incident notifications into Slack using Slack's forwarding email address. You can subscribe to a Statuspage(s) using Slack's unique forwarding address > confirm your subscription in the Slackbot channel > then any new incident notifications will appear in the Slackbot channel.
I know this is limited to receiving incident notifications (doesn't include component updates) and probably isn't exactly the solution you're looking for, but I hope this helps!
We still have this feature request in the backlog and I'm hoping we can get it prioritized soon. I've shared the link you provided with our product team, thank you!
We really need this too. Same use case, we want notices of outages in services we use to come into the slack channel we otherwise use for automated messages for our developers. I had this working just fine with HipChat back in the day, not sure what the holdup is here especially since y'all own both of these properties now! I can send automated messages into a slack channel from every other technology I use...
Hi @ernest.mueller perhaps the workaround I mentioned above (subscribing to a status page using Slack's forwarding email address) will suffice for now?
Just to clarify, Atlassian doesn't own Slack, but we're partners with them :) And to the best of my knowledge, we never had webhook support for end users via HipChat. We did have the HipChat integration which worked the same as the existing Slack integration (allows admins to pipe updates into their team's slack channels) but we still need to build the functionality for end-users to subscribe to notifications via Slack.
Adding support for end-user Slack notifications is definitely on the radar, and I'm going to do my best to help get this prioritized with our product team.