Manage and track PagerDuty in Slack with Actioner. Start using the app in Slack immediately after you install it.
Actioner provides a seamless Slack PagerDuty integration.
🔥 Manage your incidents through their lifecycle and track their updates in incident war rooms.
🌟 Let all responders take relevant actions with all the context needed — all within Slack.
🔎 Bring visibility on the incident resolution progress, and keep stakeholders and customers informed on the status and other significant changes.
⏰ Increase collaboration during incidents, and reduce resolution times with Actioner.
## Features
- PagerDuty notifications on Slack: Get notified of PagerDuty incidents and track & manage their lifecycle through Slack.
- PagerDuty actions on Slack: Create PagerDuty incidents from Slack using fire 🔥emoji. Assign, update incidents, and add notes or responders without leaving Slack.
- Post-incident checklist: Remind critical tasks to your incident responders in incident war rooms.
- On-call management: Hand off your on-call from Slack. Track and collect handoff requests in one channel, take the on-call with a single click and inform your colleagues from one place. Check on-call schedules.
## How it works
Actioner connects your PagerDuty & Slack and brings incident & on-call management to your teams.
Your team can report incidents by adding emojis to messages in dedicated Slack channels and tracking the status of incidents in broadcast channels.
This app brings together incident assignees, responders, on-calls, and stakeholders in war rooms, enabling them to focus on resolving incidents in Slack.
Actioner also notifies incident assignees and responders through direct messages in Slack and continues to guide them throughout the incident.
As soon as an incident is updated, Actioner keeps updating war rooms and responders by suggesting follow-up actions relevant to that update, such as acknowledging or reassigning incidents.
Along with managing incidents, this app allows your team to check who is on call in Slack.
Workflows
Send message when incident is acknowledged
This workflow sends a message to the dedicated incident channel when the incident is acknowledged.
Invite responders to incident channel
This workflow automatically invites users to the dedicated incident channel when they are added as a responder to the incident.
Acknowledge
Acknowledges the selected incident.
See incident details
Returns the details of a selected incident.
Send message when incident is reassigned
This workflow sends a message to the dedicated incident channel when the incident is reassigned.
Send message when incident is escalated
This workflow sends a message to the dedicated incident channel when the incident is escalated.
Reject on-call handoff request
Run this workflow to reject the on-call handoff request. The rejection message will be automatically sent to the on-call handoff message thread. Also, the user who suggested you will be informed with a DM.
Send message when incident is reopened
This workflow sends a message to the dedicated incident channel when the incident is reopened.
Suggest someone for on-call handoff
This workflow allows you to suggest someone for the on-call handoff. Suggested user receives a DM via Slack.
Snooze incident
Snoozes incident for the specified duration.
Merge incidents
Merges the selected incident to the target incident.
Assign incident to me
Assigns an incident to the user.
Send message when a responder is added
This workflow sends a message to the dedicated incident channel when a new responder is added to the incident.
Take on-call
Allows you to take on-call for a selected schedule.
Send broadcast message
This workflow automatically sends a message to the broadcast channel when there is a new incident on PagerDuty. Incident updates will be regularly reflected on the original message.
Send message when incident is resolved
This workflow sends a message to the dedicated incident channel when an incident resolved.
Resolve incident
Resolves the selected incident.
List incidents
Returns PagerDuty incidents.
Create incidents via fire emoji
This workflow is run when 🔥 (fire) emoji is added to a message on a selected channel. It helps users to create an incident on PagerDuty using workflow buttons.
Search incidents
Returns the search result of incidents.
Set problem reporting channel
This workflow creates a problem reporting channel on Slack with a given prefix. When someone puts a fire emoji on a message in this channel, Actioner will prompt users to create an incident in PagerDuty. If you do not specify the prefix, the channel will be created as #actioner-problem-reporting.
Update incident
Updates a selected incident.
Search services
Returns the search result of services.
Send message when a note is added
This workflow sends a message to the dedicated incident channel when there is a new note on the incident.
Subscribe to PagerDuty events
This workflow creates a webhook on PagerDuty to subscribe to incident events. You need to select a scope type to create this webhook: If you select Account as the scope type, Actioner will receive all incident events from your account. If you select Service or Team as the scope type, Actioner will only receive the incident events from the selected team/service incidents.
Set broadcast channel
This workflow creates a broadcast channel on Slack with a given prefix. When there is a new incident on PagerDuty, a summary post will be sent to this channel, and incident updates will be regularly reflected on the post. If you do not specify the prefix, the channel will be created as #actioner-broadcast
Send message when incident is unacknowledged
This workflow sends a message to the dedicated incident channel when the incident is unacknowledged.
List services
Returns the list of PagerDuty services.
Send Slack DM to PD user
This workflow automatically sends a DM to the users.
Add override
Adds override for a user to a selected schedule between the specified start and end date.
Create incident
Creates a PagerDuty incident with given input parameters.
Send message when incident priority is updated
This workflow sends a message to the dedicated incident channel when the incident priority is updated.
List on-calls
Returns the list of on-calls.
See my on-calls
Returns the on-call information for the user who run the workflow.
Find Slack user by PD user
This sub-workflow finds the Slack user mapping of a given Pagerduty user.
Add channel to report problems
To start reporting problems in Slack, run this workflow by selecting your channel. Your messages will turn into incidents when reacted with fire 🔥 emoji.
Add note
Adds note to a selected incident.
Edit broadcast message and channel topic
This workflow automatically updates the main message on the broadcasting channel and updates the dedicated incident channel topic.
Add responder
Adds a new responder request for the specified incident.
Set dedicated incident channel
This workflow automatically creates a Slack channel when there is a new incident on PagerDuty. It also invites responders to the channel, sets the channel purpose, and sends a summary message.
Get service
Returns the details of a selected service.
Escalate incident
Escalates the incident to the selected escalation level.
Send message when responder replies a request
This step sends a message to the dedicated incident channel when an incident responder replies the request.
Track incident lifecycle and send direct messages
This workflow sends direct messages to certain involved people. It triggers workflows when the PagerDuty incidents are either triggered, reassigned or a new responder is added to them
On-call handoff
Run this workflow to post an on-call handoff request to a selected Slack channel. Your colleagues can take the on-call or suggest someone directly from Slack.
Reassign incident
Re-assing someone to the selected incident.
Update priority
Updates the priority of a selected incident.
Security & Compliance
Privacy & data governance
Data retention policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:
Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.
Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.
Data archiving and removal policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.
Data storage policy
At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.
Data center location(s)
United States
Data hosting details
Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.
Data hosting company
Amazon Web Services (AWS)
App/service has sub-processors
Yes
Guidelines for sub-processors
Certifications & compliance
SOC attestation
Privacy policy
GDPR commitment
Data deletion request procedure
Security
Supports Single Sign On (SSO) with the following providers
Google, Slack, Okta
Supports Security Assertion Markup Language (SAML)
No
Has a dedicated security team
Yes
Contact for security issues
Has a vulnerability disclosure program
Yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
Yes
Has a bug bounty program
Yes
Bug bounty program URL
Requires third party authorization/connections
No
Third party services used by this app
Uses token rotation
No
Contributors
Actioner
.png){kind=spacer}
