> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/incident-management/rootly.md).
# Rootly
## Setup
Click into the App Directory from your Pylon dashboard and then click on the Rootly integration to view setup instructions. For more setup instructions see [here](https://kb.help.usepylon.com/articles/7214040778-how-do-i-integrate-pylon-with-rootly).
{% hint style="info" %}
Prerequisites: You must be a Rootly administrator to complete the integration setup.
{% endhint %}
## Usage
Usage Within the issue view, connect customer issues with the appropriate incident using the Rootly module on the sidebar. You can search for existing Rootly incidents to attach to a Pylon issue. The Pylon issue to incident link is now available across the product:
* Create a view of tickets filtered down by a specific incident
* Run reporting & analytics on how many tickets are associated with incidents
* Create differentiated automated workflows for tickets that are tied to an incident
{% hint style="info" %}
You can also automatically create Rootly incidents from Pylon issues using triggers. Set up a trigger action to create a new incident when specific conditions are met (e.g., when an issue is escalated or reaches a certain status).
{% endhint %}
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.usepylon.com/pylon-docs/integrations/incident-management/rootly.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.