> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/rootly.md).

# Rootly

Declare and manage incidents, follow-up work, and timeline events in Rootly.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Rootly    | API key        |

### Rootly

Connect to Rootly to manage incidents, action items, and timeline events.

#### Set up in Rootly

1. Prepare the Rootly account or service that the workflow will access. Grant access to the required resources and operations.
2. **API key:** Create a Rootly API key with access to the incidents you want to manage.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Rootly**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                     |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| API key       | Yes      | Create a Rootly API key with access to the incidents you want to manage. [Provider instructions](https://docs.rootly.com/api-reference/overview). |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Rootly** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create Incident

Declare a new incident in Rootly.

#### Inputs

| Field    | Type            | Required | Description                                                                                   |
| -------- | --------------- | -------- | --------------------------------------------------------------------------------------------- |
| Title    | string          | Yes      | A concise incident title.                                                                     |
| Summary  | textarea        | No       | Optional incident context and impact.                                                         |
| Severity | select (string) | No       | Select a severity or enter its Rootly resource ID. Options load from the selected connection. |

#### Outputs

| Field    | Type   | Description                                            |
| -------- | ------ | ------------------------------------------------------ |
| Incident | object | The incident, including its ID and current attributes. |

### Update Incident Status

Move an existing Rootly incident to a new status.

#### Inputs

| Field    | Type            | Required | Description                                                                                                                                                                                                                                      |
| -------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Incident | select (string) | Yes      | Select an incident or use incident.id from Create Incident or an ID from List Incidents. Options load from the selected connection.                                                                                                              |
| Status   | select (string) | Yes      | The target incident status. Rootly may require resolution or cancellation details for some transitions. Available values: In triage, Started, Detected, Acknowledged, Mitigated, Resolved, Closed, Cancelled, Scheduled, In progress, Completed. |

#### Outputs

| Field    | Type   | Description                                            |
| -------- | ------ | ------------------------------------------------------ |
| Incident | object | The incident, including its ID and current attributes. |

### List Incidents

List incidents from Rootly.

#### Inputs

| Field     | Type            | Required | Description                                                                                                                                                                                              |
| --------- | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Status    | select (string) | No       | Filter by incident status. Leave empty to include all statuses. Available values: In triage, Started, Detected, Acknowledged, Mitigated, Resolved, Closed, Cancelled, Scheduled, In progress, Completed. |
| Page      | integer         | No       | The page to retrieve. Minimum: 1. Default: 1.                                                                                                                                                            |
| Page size | integer         | No       | Maximum incidents in this page. Minimum: 1. Maximum: 100. Default: 25.                                                                                                                                   |

#### Outputs

| Field     | Type          | Description                          |
| --------- | ------------- | ------------------------------------ |
| Incidents | object\_array | Rootly incidents in this page.       |
| Count     | integer       | Number of incidents returned.        |
| Next page | integer       | Next page when more incidents exist. |

### Create Action Item

Create a follow-up action item for a Rootly incident.

#### Inputs

| Field    | Type            | Required | Description                                                                                                                        |
| -------- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Incident | select (string) | Yes      | The incident that owns the action item. Options load from the selected connection.                                                 |
| Title    | textarea        | Yes      | The follow-up task to complete.                                                                                                    |
| Assignee | select (string) | No       | Select a Rootly user or enter their numeric user ID. Leave empty to keep it unassigned. Options load from the selected connection. |

#### Outputs

| Field       | Type   | Description                         |
| ----------- | ------ | ----------------------------------- |
| Action item | object | The created action item and its ID. |

### Create Timeline Event

Record an event on a Rootly incident timeline.

#### Inputs

| Field      | Type            | Required | Description                                                                         |
| ---------- | --------------- | -------- | ----------------------------------------------------------------------------------- |
| Incident   | select (string) | Yes      | The incident that owns the event. Options load from the selected connection.        |
| Event text | textarea        | Yes      | What happened during the incident. The event is internal and timestamped by Rootly. |

#### Outputs

| Field          | Type   | Description                                     |
| -------------- | ------ | ----------------------------------------------- |
| Timeline event | object | The created internal timeline event and its ID. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/rootly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
