Incidents
Read incidents created in the report period with number, title, status, kind, start and resolution dates.
Rootly connector · Incident reports
Bring Rootly incidents, severities and services into your reports and AI assistants, with status, kind, start and resolution dates.
Updated November 2026
| Incident number | Title | Status |
|---|---|---|
| 88 | Webhook delivery delay | resolved |
| 89 | Login errors | mitigated |
| 90 | Search slow | resolved |
One Rootly organization is the data source.
Read incidents created in the report period with number, title, status, kind, start and resolution dates.
List severities with level, position and color.
See each service’s name, slug, description and creation date.
Compare start and resolution dates to see how long incidents ran.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Rootly incidents with sequential number, title, status, kind, start date, and resolution date.
Rootly severity definitions with level, sort position, and badge color.
Rootly service catalog components with slug, incident count, and creation date.
17 report fields across 3 datasets.
Search the available fields. Hover or tap a field to see what it means.
No fields match. Try another search or choose All.
Use Datapipe’s MCP access as your Rootly AI integration. Ask about open incidents and how long they took to resolve.
Example
Which incidents this month aren’t resolved yet, and how long did the resolved ones take?
List this month’s incidents without a resolved date, then compare start and resolved dates for the rest.
A Rootly key from Organization Settings, then API Keys. A read-only key is enough.
Read-only. Incidents, severities and services aren’t changed. Timelines, action items and retrospectives aren’t included.
Create your free account, then choose Rootly in Data sources.
Paste your Rootly read-only key. Add your uptime checks if you want them beside incidents.
Choose a report and destination: a sheet, Data Studio, ChatGPT or Claude.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Datapipe reads incidents from the report period with status and dates, severities, and services.
No. Reports cover each incident’s details and dates, not its timeline or follow-ups.
No. Rootly is read-only in Datapipe, and a read-only key works.
Yes. Add each organization’s key as its own data source; each one counts as one data source.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
One for each Rootly account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Start free, add Rootly and bring its incidents into the tools you already use.