Skip to main content

(I’ve submitted this as a support request but I thought I’d drop it here as well for a wider audience…)


We have licensed PD for all of our support/devops staff. However, we want to let other company staff create incidents. They don’t need to manage them or anything; they don’t need to be Pagerduty users at all. They just need to create them.


We have Slack integration set up, and I had hoped non-PD-users could use /pd trigger to create incidents, but it appears that can only be used by registered PD users.


It appears maybe email integration could be used by anybody, even a non-PD-user? I haven’t looked into it yet.


But is there a better way to do this? /pd trigger would have been ideal, but if everyone in our company needs to have a PD account, that’s a non-starter for us. Thanks.

Denis - Look into the Slack Workflow Builder support provided by our Slack v2 integration. You can create a simple workflow experience allowing anyone - not connected to PagerDuty - to create a PagerDuty incident.




Hey all, I’m running into the same issue as Denis. I could start another thread but this seems to be the most relevant.


Workflows would have been perfect in our case but is there a way to let users choose the priority of the incident ? Usually with workflows you show the user a slack form, and then inserts variables from that form in the steps afterwards. But it doesn’t seem possible to insert variable in the Priority field in the Pagerduty step. Without any priority, the workflows would be pretty hard to use with a large volume of incidents.


Is there something I’m missing ?

With the new Status Page offering, maybe that’s the best place for this to be done (reporting an issue for a service) ?

Running into the same limitations. It seems Slack has deprecated the legacy workflow builder now, so there doesn’t seem to be any way for folks to trigger incidents from Slack without a pagerduty account now.


Bumping this thread, in hopes of someone having a solution (or our friends over at PD to prioritise such a feature, perhaps!)

@emma matsubara, thanks for sharing this here. You’ve come to the right place!


Latest update is that the Slack Workflow Builder functionality is currently being restored.


With Slack’s recent migration from legacy workflows to the new Workflow Builder, ownership of PagerDuty’s Slack Workflow Builder Step Trigger PagerDuty Incident was transferred to and upgraded by Slack. With Slack’s new version of Workflow Builder, Slack users must have a PagerDuty account to successfully run the Trigger PagerDuty Incident workflow step.


To enable any Slack user to trigger an incident via Slack’s new version of Workflow Builder, PagerDuty is partnering with Slack to update the workflow step.


We’ll drop more news as soon as we see more developments!

I wonder how this work is going. I think what I’d like is for anyone in my company slack to create a low-urgency incident, and then allow only PagerDuty users to be able to escalate that to a high-urgency incident. That way we can give a potentially-abused power to a wider audience (we’re small enough that we can do that), but we don’t let just anyone wake up our on-call person.

Hello @ryan hiebert,


The R&D team continues to investigate the best solution to this. In the meantime, users seeking to trigger incidents using the new Slack Workflow can now mimic the behaviour of legacy workflows.


This entails configuring the step of incident triggering within the workflow to execute on behalf of a specific user:


05


34

Reply


Terms & ConditionsCookie settings