Back to Changelog
Back to Changelog

December 8, 2022

Others

Trigger Workflow from Other Workflows

Trigger Workflow from Other Workflows

💫 Trigger Workflow from Other Workflows

Workflows in Rootly can be triggered a number of ways. Manually, API, alerts, or based on specific conditions.

We are launching the ability to trigger workflows from other workflows. This provides granular control over exactly when specific workflows should run that may not be satisfied by our out of the box conditions.

This enables the ability to have nested workflows, create dependencies, and run a series of workflows all at once. The use cases are endless.

This can be found under Workflows > Tasks > Trigger Workflow.


🌝 New & Improved

🆕 Scheduled maintenance now supports custom fields
🆕 Auto-refresh option for metrics to continuously poll latest data, option to turn off as well
💅 Users declaring an incident for the first time will be prompted an optional interactive tutorial
💅 Increased API rate limits
💅 /incident overview displays incident roles and assignee
🐛 Fixed issue where team members page did not refresh upon search
🐛 Fixed issue where Rootly status page SMS notifications were not firing

Previous post
Previous post
You are viewing the latest post

Backfill and Import Past Incidents

Customizable Interactive Tutorials

Workflow Debugger

Required, Default, and Customizable Fields

Zapier Integration

Scheduled Maintenance

Branded Emails and Custom SMTP Server

🕵️On-Call Schedule Owners & Gap Finder

Incident Variable Explorer

Statuspage.io Integration - Component & Template Support

Sandbox Environments

Rollbar Integration

Beautiful Incident Timeline Pages

Manage Workflows via API, Terraform, and Pulumi

Customizable Incident Metrics

Microsoft Teams Integration

Microsoft Azure Active Directory SSO Integration

Backstage Integration

Linear Integration

Workflow Versioning

Incident Feedback

Retroactively Create Incidents and Modify Timestamps

Pulumi Provider for Rootly

Notion Integration

SCIM