Backstage Integration

🏟️ Backstage Integration - Service Catalog

We are excited to announce our Backstage integration on the Backstage Plugin Marketplace.

Backstage is a popular service catalog tool open sourced by Spotify and is used by companies such as Netflix, DoorDash, Hello Fresh, and 100's of others including many of our customers.

We continue to reduce the fragmentation of tooling by building the most pluggable enterprise-ready incident management platform on the market.

Customers can substitute their Rootly service catalog with their existing Backstage implementation and seamlessly ensure both platforms remain in sync.


  • Easy to install by leveraging the official Rootly + Backstage plugin:
  • Import services created and managed in Backstage directly to Rootly
  • Create incidents in Rootly that pull from service impact directly from Backstage
  • Double click on services in Backstage and browse their respective incident history depending on what was impacted in Rootly
  • Browse incident metadata as granular as per service in Backstage such as severity, reporter, status, start/end time, etc.
  • Shortcut to create incidents in Rootly via Backstage for easy access
  • View on-going Rootly incidents in Backstage for broader visibility

In Action

Getting started guide:

🌝 New & Improved

  • πŸ†• Workflows for postmortem with status conditions (Draft, Published)
  • πŸ†• Incident variables for roles such as {{ incident.commander }}
  • πŸ†• Custom Fields now show up in Metrics
  • πŸ†• Option to cancel queued Workflows
  • πŸ†• Workflow task for Send Slack Message now includes the ability to add an action button for Esclating an incident
  • πŸ†• Versioning for Rootly postmortem templates
  • πŸ†• ServiceNow supports custom fields mapping of incident metadata
  • πŸ†• Workflow task for Sending Slack Message available under Action Item workflows
  • πŸ’… Ability to handle organizations with thousands of GitHub repositories for efficiently
  • πŸ’… Schedule Postmortem Meeting task can now exclude weekends
  • πŸ’… Workflow template for renaming a Slack Channel to a Jira ticket number
  • πŸ’… Ability to export metrics to PDF
  • πŸ’… PagerDuty and Opsgenie paging tasks in Workflows can now auto-match or select priority levels
  • πŸ’… Additional Workflow triggers such around creation and update of Postmortem and Causes
  • πŸ› Fixed issue where test/training incidents were appearing on the Rootly dashboard and summary emails
  • πŸ› Fixed issue on UI where pop-up modules rendered without the background

Linear Integration

🎟️ Linear Integration

It's no secret that Rootly has a powerful integration with Linear and is leveraged by customers already.

Today, we are formally launching in partnership with Linear on their integrations marketplace.

Customers will be able to automatically create and track tickets such as incident action items in Linear and ensure they bi-directionally sync. This can all be done from within Slack or Web.

  • Create a Linear issue when a new incident is created with relevant metadata
  • Create a Linear sub-issue when a new action item is created
  • Update an issue ticket to Done when an incident is resolved


  • Full customization and configuration via Workflows
  • Automate routing different Linear tickets to different boards depending on incident severity, type, team, or any other condition
  • Automatically sync incident severity with Linear priorities
  • Leverage incident variables to populate to customize ticket description, title, etc.

In Action

🌝 New & Improved

  • πŸ†• Add custom message when paging via Workflows to help provide more context, incident variables are also supported
  • πŸ†• Shortcut buttons pop up with common tasks in Rootly during long periods of inactivity to prompt if you need help, can be configured further in Workflows
  • πŸ†• Role-based incident variables (e.g. Send Slack message to Incident Commander)
  • πŸ†• Custom fields (e.g. customer impact) show up in Slack as part of the incident overview and is easily editable
  • πŸ’… Search and filtering capabilities to services and functionalities attribute in the Rootly API
  • πŸ’… Additional guidance for modifying custom wizard fields on Slack and Web
  • πŸ’… Action items view on Web by default exclude tasks and focuses on follow-up actions
  • πŸ’… UX improvements to incident summary in the Slack incident overview section to make it easier to digest
  • πŸ’… Error message when running a Slack command in an incident channel but that incident has been already deleted on Web
  • πŸ’… /incident help UX improvement to make finding and learning commands easier, does not require clicking into each one
  • πŸ› Fixed issue where date picker did not allow today to be set
  • πŸ› Fixed issue where assigning an action item to team did not immediately reflect in Slack
  • πŸ› Fixed issue where playbooks did not populate their respective checklist of tasks when incident was updated

Workflow Versioning

πŸ—„ Workflow Versioning

Introducing Workflow Versioning, a detailed audit trail and history of all changes made to a given Workflow.

Workflows are at the heart of Rootly. By making it easier to track changes made over time, teams will find Workflows even easier to manage and safely collaborate together than it already is.

Why? Previously, there was little to no visibility who made the change or what they were. Now there is a mechanism to quickly see what changes were made without needing to recall from memory and compare each Workflow attribute.

  • Visually pleasing so at a glance changes from one version to another are obvious (e.g. colour coding)
  • Version numbers and date changed
  • User that executed the change
  • The changes themselves track both past to present differences for all Workflow attributes (e.g. trigger, condition, task, etc.)

Existing customers can access this feature by heading into Rootly > Workflows > Clicking on any Workflow name > Versions.

🌝 New & Improved

  • πŸ†• Display in incident timeline all users that join the incident channel regardless if they're a Rootly user
  • πŸ†• Ability to filter by incident attributes in Rootly API
  • πŸ’… External postmortems on Confluence, Google Doc, Notion, and others display follow-up action items only, excluding tasks
  • πŸ’… Fresh coat of paint for with accessible links to G2 customer reviews
  • πŸ’… Naming for Rootly Incident Page is now aligned across both Web and Slack
  • πŸ’… Ability to delete Rootly generated postmortems
  • πŸ› Fixed issue where custom Workflow trigger commands in Slack weren't working
  • πŸ› Fixed issue where UI on Confluence and Google Doc postmortems had incorrect line spacing
  • πŸ› Fixed issue where occasionally private incidents were accessible via postmortem view
  • πŸ› Fixed issue where running /incident convert did not let you pin events to the incident timeline

Incident Feedback

✍️ Incident Feedback

Like organizations, your incident response process will evolve over time. We are making learning from incidents your superpower by closing the feedback loop.

Excited to announce the ability to collect incident feedback and data on the incident process. This will help reveal what is working and areas of improvement (e.g. communication).

Purposely designed to be accessible, feedback can be collected in Web or Slack, by default responders are automatically prompted when incident is mitigated/resolved or by running /incident feedback.


  • Fresh and accurate - gather feedback while still fresh and relevant instead of relying on postmortem review meetings a week late or manual surveys
  • Data - incidents scored on satisfaction and given an average ⭐ rating and text field for long form responses
  • Sample size - gather feedback from all incident responders and from those that would be less likely to voice their feedback for a holistic picture
  • Flexible - can use Workflows to modify feedback prompt timing and instructional text
  • Psychological safety - incident responders can submit feedback anonymously

🌝 New & Improved

  • πŸ†• Can define default roles for new users that join Rootly (e.g. Admin, Users, Observer, Commander, any custom created) in organization settings
  • πŸ†• Custom fields can be toggled on/off
  • πŸ†• Custom fields in Slack can be updated at any time and can be managed separately
  • πŸ†• Slack bots (including homegrown) other than Rootly can be automatically invited to incident channels just like responders
  • πŸ†• PagerDuty alerts Rootly pipes into Slack now include a link to PagerDuty for reference
  • πŸ†• Workflows can specify which days of the week to run (e.g. work days only M-F)
  • πŸ†• Workflow for updating Google Doc postmortem
  • πŸ’… API Reference revamp using Stoplight:
  • πŸ’… If pinning a Slack message to incident timeline fails, we provide a helpful error message
  • πŸ’… Loading speed improvements in Slack when drop-down lists are long
  • πŸ’… Notion task in Workflows now have the ability to select pre-canned postmortem templates in Rootly
  • πŸ’… Custom fields now display in Notion generated postmortems
  • πŸ’… Slack buttons in incident channels are shortened to reduce visual clutter
  • πŸ’… All new Rootly accounts by default post incident updates in threads instead of broadcasting to channel
  • πŸ’… Workflows are categorized by enabled and disabled
  • πŸ› Fixed issue where on rare occasions duplicate incidents were being created

Retroactively Create Incidents and Modify Timestamps

⏲️ Retroactively Create Incidents and Modify Timestamps

Declaring an incident the moment it actually starts may not always be possible. Sometimes we notice incidents hours or days later. This causes skewed timestamps that paint an inaccurate metrics picture.

We are announcing the ability to retroactively create incidents and modifying all timestamps (started, detected, acknowledged, mitigated, resolved).

Easily backfill past incidents and accurately reflect actual start and resolved times.

  • Available at incident creation on Web and Slack as "Change start time" field
  • User timezones displayed when selecting new date and time
  • Modifying timestamps available on Web (per incident) and Slack (/incident timestamp), accessible at anytime of the incident
  • Built in guardrails to prevent e.g. Resolved occurs before Started
  • Metrics automatically get updated

🌝 New & Improved

  • πŸ†• Export incident timeline to CSV, JSON, XML format (found at the bottom of your timeline)
  • πŸ†• Creating new incidents now showcase ongoing incidents to ensure duplicates are not created in both Web and Slack
  • πŸ’… Workflow task for Jira now supports Due date attribute
  • πŸ’… Infrastructure enhancements as our customer base continues to rapid grow
  • πŸ’… Placeholder text in Web provide better guidance when you haven't created your first incident or postmortem
  • πŸ’… Workflow task for Shortcut can now map to assignee
  • πŸ› Fixed issue where marking an action item as canceled in Slack did not accurately reflect the number of open items

Pulumi Provider for Rootly

βš—οΈ Pulumi Provider for Rootly

Hot on the heels of our API and Terraform provider, we are excited to launch our Pulumi provider!

Support for Pulumi further helps Rootly build our lead for being the most developer friendly and Infrastructure as Code ready incident response platform.

Pulumi is a IaC platform that leverages existing programming languages such as TypeScript, JavaScript, Python, Go, .NET, Java, etc.

Engineering teams can now manage Rootly directly in code making distributed ownership of their service ownership even easier.

No more needing to click into the Web platform to manage configurations, example use cases:

  • Manage teams and roles
  • Manage severities, incident causes, types, etc.
  • Import infrastructure such as services and functionalities

Learn More


🌝 New & Improved

  • πŸ†• Guidance - reminder to update summary if one hasn't been set (configurable in Workflows)
  • πŸ†• Guidance - reminder to assign roles if none have been assigned (configurable in Workflows)
  • πŸ†• Send Slack message Workflow task now supports sending to users assigned to a specific role (e.g. Commander, Scribe)
  • πŸ†• All time and date selectors inside of the Web platform display the users timezone
  • πŸ†• Pinned images and screenshots from Slack now appear in Notion postmortem
  • πŸ†• Alerts and Pulse Workflow conditions can be triggered by specific webhook payloads
  • πŸ†• Grafana integration supports taking snapshots of specific graphs
  • πŸ’… All new accounts on Rootly have additional default Workflows (based on best practices) such as auto-archive incidents, assign role / update summary reminders, and prompts for incident feedback
  • πŸ’… Continued investment across monitoring and observability to further improve our reliability
  • πŸ’… Shortcut integration supports linking to epics
  • πŸ› Fixed issue where action items did not also appear on the incident timeline
  • πŸ› Fixed issue where Notion failed to create a postmortem page under extremely rare race conditions

Notion Integration

πŸ“œ Notion Integration

We are excited to partner together with our friends at Notion and be featured on their integration marketplace.

Customers can now enjoy automatically generated postmortems and incident timeline where they document work already, Notion.

With Rootly + Notion installed, customers can:

  • Create incident timelines automatically in Notion without copy-pasting from Slack
  • Automatically populate incident metadata (e.g. severity, resolution time, service impact, etc) for consistent data every time
  • Depending on the type of incident, different postmortem templates are dynamically used
  • Jira tickets are automatically linked, e.g. action items

Learn more

Read full release by Notion:

Find Rootly on Notion integration marketplace:

🌝 New & Improved

  • πŸ†• Quick access selector for incident variables in the postmortem editor
  • πŸ†• Launched on Product Hunt 😸
  • πŸ†• Incident variables for {{ incident.started_by }}, {{ incident.mitigated_by }}, {{ incident.resolved_by }}, and {{ incident.cancelled_by }}
  • πŸ†• Incident variables for {{ incident.mitigation_message }} and {{ incident.resolution_message }}
  • πŸ†• Ability to view and export Rootly status page subscribers
  • πŸ’… Redesigned making it even easier to navigate and discover
  • πŸ’… Redesigned sign up and sign in pages
  • πŸ’… Removed unnecessary links back to Rootly inside of various Slack event messages to reduce noise
  • πŸ’… No longer alert the user assigned a particular role if the user assigning the role is the same
  • πŸ’… Cleaned up copy around editing links in Slack to be more intuitive
  • πŸ’… Slack channels within the Rootly platform can be searched with or without a hashtag # channel-name
  • πŸ’… Delightful thank you page whenever you sign up for a personalized demo
  • πŸ’… Cleaned up how incident timeline toggles are displayed (e.g. only show starred events)
  • πŸ› Fixed issue where Rootly postmortem editor was occasionally not saving


πŸ‘ͺ SCIM (System for Cross-domain Identity Management)

SSO and SCIM goes together like peanut butter and jelly.

We are excited to introduce SCIM to continue solidifying Rootly as the most enterprise-ready incident management platform on the market.

SCIM ensures your user data is secure and automates the user identify lifecycle (e.g. automatic deprovisioning).

What can you do?

  • Provisioning - onboard all your users onto Rootly at once
  • Creation - automatically create users in Rootly when you create a new user in your identity provider (all are supported)
  • Deactivate - automatically remove users in Rootly when you delete a user in your identity provider

Does it work with any identify provider?

Yes! We are using SCIM 2.0 standard and compatible with any identity provider (Okta, Azure AD, Google, etc.)

Existing customers can try it today by visiting our Documentation.

🌝 New & Improved

  • πŸ†• Edit timestamps directly from Slack with /incident timestamp (e.g. Starting, Detected, Acknowledged, Mitigated, Resolved, etc)
  • πŸ†• Creating an incident from alerts that Rootly ingests now allow you to update incident details first instead of automatically declaring it
  • πŸ†• Ability to customize alert payload with custom incident copy and incident variables when you page from PagerDuty / Opsgenie
  • πŸ†• Services and Functionalities now support importing from Opsgenie
  • πŸ’… Multiple company email domains can be used in a single Rootly workspace
  • πŸ’… Postmortem custom fields are now separated by Rootly generated and external generated (e.g. Confluence, Google Docs)
  • πŸ’… Better support for organizations with multiple workspaces in how we handle cross-channel interactions
  • πŸ’… Changes and modifications to timestamps now show up in the incident timeline
  • πŸ› Fixed issue where pinning images to incident timeline from Slack occasionally did not work first try
  • πŸ› Fixed issue where the order of events on incident timeline were incorrect
  • πŸ› Fixed issue in Google Docs workflow task where selecting a drive folder did not populate

Custom Fields

🌿 Custom Fields

The most configurable incident management platform just got even more flexible!

We are announcing the ability to define custom fields anywhere in Rootly to ensure unique incident data can be captured, even if they're customer specific.

Endless use cases

  • Which customers have been impacted?
  • How the incident was detected?
  • Revenue impact?
  • What geographies were impacted?
  • Were the right responders part of the incident?
  • etc...

Customizable for any use case

  • Supports both Slack + Web platform and can be separately configured
  • Determine where custom fields should be captured: incident creation, mitigation, resolution, or postmortem
  • Pick between single select, multi-select, and free text custom field types (more coming soon!)
  • Set the fields as either optional or required

Are Workflows supported?

Yes! Any custom field defined will show up as a new condition inside of Workflows. That means you can run Workflows based on custom field inputs (e.g. emailing a specific customer when they are impacted).

Existing customers can try it today by visiting Configuration > Custom Fields.

🌝 New & Improved

  • πŸ†• Trigger in Workflows for when roles (e.g. commander, scribe, etc) are assigned
  • πŸ†• Ability to update Rootly generated integration links via /incident integrations command (e.g. replace Zoom bridge with existing one)
  • πŸ†• See why our customers rated us ⭐⭐⭐⭐⭐ on G2!
  • πŸ†• Import PagerDuty services to Rootly functionalities
  • πŸ†• Incident updates (Mitigated, Resolved) in main incident announcement (#incident, #warroom) channel have the option to be threaded
  • πŸ’… Owner has been renamed to Reporter to bring greater clarity who created the incident
  • πŸ’… Incident variable {{ incident.subscribers | map :email }} to invite any participant in the incident to postmortem review meeting
  • πŸ’… Running /incident help brings up all Rootly commands faster
  • πŸ’… Better support for PagerDuty escalation policy when auto assigning roles
  • πŸ’… Descriptions for roles support markup and links by default
  • πŸ› Fixed issue where modifying incident timestamps weren't saving
  • πŸ› Fixed issue where users without permission to invite teammates still saw the option (although it didn't work for them)

Automatically Schedule Postmortem Reviews

πŸ“† Automatically Schedule Postmortem Reviews

Reviewing and learning about your incidents in a blameless way is critical to improving your incident management program.

We are making scheduling postmortem review meetings even easier via a new Workflow task.

  • Supports Google Calendar
  • Dynamically add attendees to the review meeting based on involvement with {{ incident.subscribers }}
  • Add permanent attendees (e.g. Infrastructure manager)
  • Set how long after the incident is resolved and duration of meeting

More importantly, build discipline and habits around coming together and sharing incident knowledge.

🌝 New & Improved

  • πŸ†• Integration links on Web platform are editable, e.g. you want to use an existing Zoom bridge and not the one Rootly generates
  • πŸ†• Confluence uses the latest version called "new editor"
  • πŸ†• Browsing available commands in /incident help now lets you directly execute them without retyping the slash commands
  • πŸ’… Full sized image import in Google Doc postmortem timeline for any pinned item
  • πŸ’… Ability to unsubscribe from transactional incident update emails
  • πŸ’… New icon displayed next to major new features
  • πŸ’… Easily access Rootly's blog and changelog at the bottom of every weekly summary email to stay up to date
  • πŸ’… Incident Slack channel URLs are hyperlinked in timeline on Web platform to reduce visual clutter
  • πŸ’… If users manually connect their Slack account via /incident connect, we now display a confirmation message to show it was successful
  • πŸ› Fixed issue related to postmortem timeline formatting on Confluence
  • πŸ› Fixed issue related to duplicate incidents being displayed on rare occasions

Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.