Marketers
See which channels and pages bring visitors who convert.
Review Rootly incident statuses, severity definitions and service incident counts in a read-only data source.
Updated November 2026
| Incident number | Title | Status |
|---|---|---|
| 88 | Webhook delivery delay | resolved |
| 640 | How we pack orders | draft |
| 210 | Pricing page refresh | future |
See which channels and pages bring visitors who convert.
Get a weekly traffic summary without opening another dashboard.
Send each client the same clean traffic report every month.
Read incidents, severities and services using your Rootly API key.
Datapipe reads Rootly data for reports. It never changes anything in Rootly.
Incidents and services are never modified.
Combine incident timelines, severity levels and service counts in one report.
An API key or token from your Rootly account.
Read access only. Datapipe never changes anything in Rootly.
Read-only. Incidents and services are never changed, and timelines, action items and retrospectives are not included.
Incidents, severity definitions, and service catalog records from Rootly.
Read-only reporting access using your Rootly API key. Incidents and services are never modified.
Read-only. Incidents and services are never changed, and timelines, action items and retrospectives are not included.
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.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Summarize Rootly incidents, severity definitions, and service catalog incident counts.
checkout-api logged 4 resolved incidents while core-auth recorded 1 minor incident.
Rootly incidents with sequential number, title, status, kind, start date, and resolution date.
Use this template →Rootly severity definitions with level, sort position, and badge color.
Use this template →Rootly service catalog components with slug, incident count, and creation date.
Use this template →Create a project and choose Rootly in Data sources.
Pick where it goes. This one sends the numbers to Snowflake.
Pick where it goes. Choose incidents, severities or services and a destination.
| Incident number | Title | Status | Started at | Resolved at | Service name | Description |
|---|---|---|---|---|---|---|
| 88 | Webhook delivery delay | resolved | 1,240 | 1,240 | 1,240 | Card payment |
| 640 | How we pack orders | draft | 640 | 640 | 640 | Refund |
| 210 | Pricing page refresh | future | 210 | 210 | 210 | Invoice |
Sample numbers, so you can see the shape. Your report uses your accounts.
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.
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.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
This integration is read-only in Datapipe. You can report on Rootly, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Rootly. Read-only reporting access using your Rootly API key. Incidents and services are never modified.
This page lists 17 report fields across 3 datasets. You pick the columns when you build the report.
Incidents, severity definitions, and service catalog records from Rootly. Account permissions and the records available from the provider determine which rows can be read.
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.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Rootly when you are ready.