Back to Changelog
Back to Changelog

August 17, 2023


Automate Component Status Updates on

Automate Component Status Updates on

⏱️ Automate Component Status Updates on

We've made an exciting upgrade to our integration: customers using can now use Rootly to automatically update component statuses. Prior to this upgrade, teams that wished to mark a specific component as operational, degraded_performance, partial_outage, major_outage, under_maintenance, or offline, would need to manually publish to their status page. This upgrade enables you to simply set up your workflow(s) once, and Rootly will automatically publish to the status page and place each component in the correct status.

How it Works:

  1. Connect your account. You’ll simply need to link your account with your Rootly account once, and you're ready for configuration!
  2. Import an existing status page. Use an existing page from your account instead of creating a net new in Rootly.
  3. Leverage the power of JSON and Liquid. The advanced setup section in the Publish Incident to Status Page task allows you to set the exact component(s) you want to update and the status(es) you want to set them to.
  4. Automated task using a workflow. Once a trigger event occurs, Rootly automatically detects the change and updates the component(s) status(es) on your page. This means your page stays up to date without any manual intervention.
  5. Notify subscribers in real time. The workflow will also handle real-time notifications to keep stakeholders, customers, and internal teams informed on each status change.

Why it Matters:

  • Improved Incident Response SLA: By automating status updates from, Rootly ensures that the right people are alerted at the right time, reducing your Mean Time To (MTTx) metrics.
  • Enhanced Transparency: Real-time system health updates foster transparency and trust with customers and stakeholders. Which in turn, enhances your reputation and overall customer experience.
  • Increased Efficiency: Eliminating manual status updates allows your team to focus on incident resolution, rather than administrative overhead.
  • Streamlined Communication: Consistent and accurate incident updates across all channels provides clarity during high-pressure situations.

Checkout this short video to see a sample use case and learn how to set it up:

🌝 New & Improved

🆕 Added user_id as an optional request body parameter to the Create a Incident API to allow teams to programmatically create incidents on-behalf of another user
💅 Added Cancel button to escalation dialog on web UI to improve visual consistency across all platform dialogs
💅 Improved user experience by dynamically displaying subscription options on status pages based on the enabled subscription methods
🐛 Fixed spotty Slack command responses for multi-org accounts integrated to Slack Enterprise
🐛 Fixed incorrect private user display in Slack incident channels

Previous post
Previous post
You are viewing the latest post

🔌 Generic Webhook Alert Source

🔒 Lock Individual Workflows

🐦‍⬛ Round Robin Escalation Policies

🚨 Alert Sources

🔔 Configurable On-Call Shift Reminders

🪄 Dynamic Forms

🔐 Granular Role-Based Access Control Settings for On-Call

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on

🔦 Drop-down Search in Escalation Policy Builder

🦊 GitLab Integration

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform