Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rootly.com/llms.txt

Use this file to discover all available pages before exploring further.

Integrations connect Rootly with the tools your teams already use, such as alerting platforms, collaboration tools, ticketing systems, and internal services. By connecting these systems to Rootly, you can automate incident workflows, sync data across tools, reduce manual coordination, and keep responders working in the systems they already know.

​
What Is an Integration?

An integration is a connection between Rootly and another system. That system might be a third-party product or custom software built by your organization. Rootly supports a wide range of integrations across categories such as:
  • Communication and collaboration
  • Alerting and on-call
  • Observability and monitoring
  • Issue and project tracking
  • Video conferencing
  • Automation and AI
Popular examples include PagerDuty, Jira, Zoom, Kubernetes, and GitHub.

​
How to Use This Section

Use the Integrations navigation on the left to browse available integrations by category. Most integration sections include documentation for:
  • Overview
  • Installation or setup
  • Workflow actions
  • Alerting behavior, when supported
  • Integration-specific configuration
If you are setting up a new integration, start with that integration’s main page and then follow any linked installation or workflow guides.

​
Custom Integrations

If you want to connect Rootly to internal tooling or build your own integration, use the API documentation to get started. This is useful for organizations that want to extend Rootly with custom automation, internal systems, or proprietary workflows.

​
Security

  • Integration keys are encrypted at rest using AES 256-bit encryption and protected by TLS in transit.
  • Key management is in place for encryption keys used by production services.
For stricter network controls, see the documentation for Rootly outbound IP allowlisting if your organization restricts incoming traffic by source IP.