Rootly | The Rootly Edge Connector

The Rootly Edge Connector lets you securely integrate internal services, monitoring tools, and automation workflows with Rootly—even if those systems live behind your firewall. By deploying the Edge Connector within your network, you can safely send alerts, trigger workflows, and interact with Rootly APIs without opening inbound access to your environment.

Why it matters

Many enterprise environments operate in restricted networks where exposing services to the internet is not allowed. Historically, this created friction when integrating internal monitoring or operational tools with external incident management platforms.

The Rootly Edge Connector solves this by establishing a secure outbound connection from your infrastructure to Rootly. This allows your teams to:

Integrate internal monitoring systems that cannot be exposed publicly
Trigger incidents, alerts, or workflows from private environments
Maintain strict network security policies without compromising incident response automation
Connect on-prem systems to Rootly with minimal operational overhead

How it works

Deploy the Rootly Edge Connector inside your network or private infrastructure.
The connector establishes a secure outbound connection to Rootly.
Internal systems can then communicate with Rootly through the connector to send alerts, trigger workflows, or interact with APIs.

This architecture ensures that no inbound firewall rules or public endpoints are required, making it ideal for regulated or security-sensitive environments.

Getting started

Deploy the Edge Connector within your internal network.
Configure it with your Rootly credentials and environment settings.
Connect your internal systems to the connector to start sending alerts or triggering Rootly workflows.

Check out the docs to learn more and get started.

With the Edge Connector, Rootly becomes easier to integrate into high-security and on-prem environments, enabling teams to automate incident response while keeping their infrastructure fully protected.

New & Improved

New Features

The /oncalls API response now includes schedule and escalation policy names, not just IDs
Live call routing now redirects callers to voicemail within the same alert when no callable targets are found, rather than creating a separate alert
The deleted alert field modal now includes a clickable link to the associated escalation policy
API error messages now include more descriptive context when a bad request causes a 500 error
Slack notifications sent from the comms module are now ephemeral — only visible to the user who sent the communication, reducing noise in incident channels
Incidents API now supports filtering by slack_channel_id via filter[slack_channel_id]
Microsoft Teams meeting chats are now stored as a separate, referenceable property on incidents, enabling new template variables
SCIM Groups from identity providers (e.g., Google Workspace) can now be synced to Rootly Groups/Teams
When deleting an object that has dependants, those dependants are now shown as clickable links
Phone numbers are now included in the member export
Incident parent/child relationships can now be reversed or removed after the fact
The JSON Path Explorer tool is now linked in the navigation help section for easier discoverability
The Alert Source page no longer auto-refreshes when new alerts arrive, making it usable for high-volume sources
Slack alert messages now include a direct link to the incident's Slack channel when an incident is created from or linked to an alert
The meeting bot can now be configured to record audio only (no video)
Slack integration setup now has clearer labels: "Connect to Slack Enterprise Grid" vs "Connect to Single Workspace"
Terraform provider now supports section_order for rootly_status_page resources
Retrospective publishing flow has been updated

Bug Fixes

Preferred name can now be updated via the PUT /v1/users/:id API
Improved reliability of email alert sources to consistently create alerts
Shift update notifications are now sent once per schedule update
Alerts now sort correctly when sorted by "Most recent"
Non-paging alert timelines now correctly show a single status entry without briefly flipping to "Triggered"
Alert timelines on the manual page no longer show unexpected events
Generic webhook alert creation now returns the alert ID in the API response
The PATCH alert API endpoint now correctly merges field values instead of overwriting them
Shadow users no longer receive notifications that they are shadowing themselves
API access restrictions now correctly return 403 instead of 200 when a request is blocked
Only workflows with a manual trigger now appear when triggering a workflow from an incident
Schedule filters now reset correctly when removed, and no longer persist on navigation
The Slack channel link now appears on the alert block immediately when an alert is created
Workflows now reliably trigger once per event
Backfilled incidents now correctly affect service and functionality uptime on status pages
Azure AD sync now correctly resolves last names without duplication
Playbooks now trigger correctly when an incident's cause field is updated
Comment drafts are now preserved when navigating away from an incident
Custom domain status pages now display their own description in link previews instead of Rootly's
The "Subscribe to updates" button on status pages with custom domains now works correctly
The FreshService integration is now correctly labeled throughout the UI
The "Learn more" link on the Alert Grouping page now points to the correct URL
Functionalities now sort correctly in alphabetical order
Default Slack messages are now sent once on incident creation
Rootly bot updates posted to Slack threads now render with correct formatting
Cancelled workflow runs no longer reset the inactivity timer
The timestamp editing popup is now correctly aligned on smaller screens
"Closed" incidents are now counted in the "Resolved" total on the home dashboard
The payload condition link in alert workflows now navigates to the correct page
rootly incidents get and rootly incidents list CLI commands now work correctly for all orgs
Images now appear consistently in exported retrospective documents