> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/incident-management-and-scheduling/rootly.md).

# Rootly

<div align="left"><figure><img src="/files/S860rLvNTj8HBZYoh3DO" alt="" width="128"><figcaption></figcaption></figure></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Rootly**

1. Find the **Rootly** integration module under the **Scheduling** section.
2. Click the **Connect** button.
3. Enter a Rootly **API Key**

{% hint style="info" %}
You can access or create an API Key by visiting **Configurations > API Keys > Generate New API Key** in Rootly. Visit Rootly's [documentation](https://docs.rootly.com/api-reference/overview#how-to-generate-an-api-key) for more info.
{% endhint %}

### Configure the Rootly integration

1. Choose a Schedule from the dropdown that will be used to assign release pilots to releases in Runway.

Release pilots will first be assigned to releases in Runway by matching up *target kickoff dates* to shifts in the configured Schedule in Rootly. The user that's scheduled to be on-call on the target kickoff date of a given release will be assigned as release pilot when the release is created.

{% hint style="warning" %}
You will not be able to re-assign or override release pilots in Runway if a Scheduling integration is connected. You must manage release pilots and overrides from Rootly directly.
{% endhint %}

For more details on how the Scheduling integration affects the release pilot rotation in Runway, visit the [Release pilot rotation docs](/using-runway/app-settings/release-pilot-rotation.md#using-a-scheduling-integration-to-manage-the-release-pilot-rotation).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/integrations/incident-management-and-scheduling/rootly.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.