Find Out Who is On-call Via Slack


(Marion Clelland) #18

Hey everyone!

We were also having the same problem here are IBM. We’ve created a sample flow in IBM App Connect that is available for others to add to their own IBM App Connect account and modify as they require. You can provision a trial version (Lite plan) for free through IBM Cloud and search for the App Connect offering from the Catalog: Once you have provisioned an instance of the service navigate to Templates and look for Get PagerDuty schedule and update Slack user group and topic. We already have some ideas on how we are going to improve it but would welcome feedback from the PD community too!


Marion (IBM)

(Sean Higgins) #19

Hi all -

Sean here from the Product team at PagerDuty. Thanks for the various suggestions around this feature. Good news – this is on our roadmap for the Slack integration and the functionality will be available in the core integration.

Let me know if you’re interested in joining the early access program. This will be kicking off in the new year.



Hi @sean, I’d definitely be interesting in joining the early access programme when it starts. :+1:


(David Smith) #21

+1 for early access @sean, please let me know the details when available.


(Elmer Millikan) #22

Here at Echo we would be interested in this functionality. Thanks.

(Marion Clelland) #23

@sean We’d like access too :slight_smile:

(cmeury) #24

Same here.

(Eran Gilon) #25

Hi @sean,
I’d also be very happy to join early access for this.

(Mudassir Razvi) #26

Would love to be part of early access


Very interested in trying early access for this feature. Would love to know if my team can participate.

(Leonardo Rosales) #29

Hey @sean we’d like to join the early access program.

(Ben Chen) #30


We would also be interested in joining the early access program.



(Colin O'Dell) #31

Hey @sean we would love to join the early access program as well!

(Casey Fischer) #32

hi @sean, i would love to know more about the early access program. thanks!

  • casey

(Sean Higgins) #33

Thanks everyone for expressing interest. Keep an eye on your inboxes in early February.

In the meantime, I’d love to understand how you’d like this type of interaction to work.

  • Are you hoping to use a slash command to view Escalation Policies or would you be looking by Service?
  • What type of optional parameters would you like to pass in (i.e “day”, “month”), if any?
  • Would you ever try to find who’s on call for a given Slack channel?

(Casey Fischer) #34

hi @sean. my team was hoping for a way to set up a slackbot that automatically posts to our ops channel every time a rotation occurs, with the names of who is now on call from our team. a slash command to view the current escalation policy would also be very useful.

thanks so much, we’re looking forward to seeing this feature in action.

(Shawn Carter) #35

Hey @sean, I would love to be included in this as well.

The ideal integration would be a slash command like /pd oncall or /pd whosoncall that would then ask you which policy/schedule you were interested in (example: Support, Support Shadow, Dev, Dev Backup) with options to pick just one or all of them. This would then spit out AGENT NAME is on call for POLICY until date/time.

Something like this would be great for our teams that want to reach out to our on call person without triggering the policy. Or just to know who’s on call.


Hi @sean ,

My team is very interested in trying out this feature when it is ready for alpha/beta.



(Mike Arwine) #37

Hi Sean,

Any update on this feature? At a minimum, I would love to be part of the early access release.


(Mikael Knutsson) #38

A bit late to the party, but we’re definitely interested in testing out a more advanced slack-integration as well.
To answer your specific questions posted later:

  1. We would most likely want to bind a Service to a room in terms of viewing who is on call
  2. I doubt anyone would use optional parameters for us (at least for now), generally we’d just want to know who is on call right now
  3. See answer for 1. Yes, most likely - though even a simpler implementation that shows everyone on call for a statically defined service would be enough for us.