Marketers
See which channels and pages bring visitors who convert.
Read & reportRead-only source
See your incident.io numbers in Amazon Redshift.
Review incident.io incident timelines, severity levels and on-call schedules in a read-only data source.
- Traffic, sources and conversions in a sheet or dashboard, refreshed for you
- A weekly traffic report nobody has to rebuild
- Ask ChatGPT or Claude what changed, using live incident.io numbers
Amazon RedshiftStart free Connect incident.io
Updated November 2026
| Reference | Incident name | Status category |
|---|---|---|
| INC-104 | Elevated API latency | closed |
| 640 | 640 | Pending |
| 210 | 210 | Refunded |
- SetupPaste a key or token
- Reads15 report fields across 3 datasets
- ChangesNone, read-only
- RefreshDaily to every 15 minutes
Who uses Datapipe with incident.io
Founders
Get a weekly traffic summary without opening another dashboard.
Agencies
Send each client the same clean traffic report every month.
What you can do with incident.io
Read and report
Read incidents, severities and schedules using your incident.io API key.
- incident.io incidents & schedules
- Incidents
- Severities
- On-call schedules
Read-only source
Datapipe reads incident.io data for reports. It never changes anything in incident.io.
Full read details
Incidents are never modified.
Examples for your team
Track incident response and on-call coverage
Combine incident statuses, severity ranks and schedule timezones in one report.
- Scheduled refresh
- Latest incident.io data
- Updated report
Before you connect
What you need
An API key or token from your incident.io account.
Read-only
Read access only. Datapipe never changes anything in incident.io.
Limits and exclusions
Read-only reporting access using your incident.io API key. Incidents and schedules are never modified.
Full details and limits
Incidents, severity levels, and on-call schedules from incident.io.
Read-only reporting access using your incident.io API key. Incidents and schedules are never modified.
Incidents, severity levels, and on-call schedules from incident.io. Read-only reporting access using your incident.io API key. Incidents and schedules are never modified.
Reports you can build
4 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- incident.io incidents & schedules
- Incidents
- Severities
- On-call schedules
What each dataset reports
- incident.io incidents & schedules
Incidents, severity levels, and on-call rotation schedules.
- Incidents
incident.io incidents with reference code, name, status category, severity, mode, and creation date.
- Severities
incident.io configured severity levels with rank and description.
- On-call schedules
incident.io on-call rotation schedules with timezone and creation date.
Metrics and dimensions
15 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.
Send incident.io data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
ClickHousePush rows into ClickHouse over HTTPS with an API key.
AWS S3Write report files to your S3 bucket with IAM access keys.Amazon RedshiftLoad rows into Redshift via the Data API with IAM keys.
FireboltPush rows into Firebolt over HTTPS with a Service Account.
PostgreSQLWrite report rows into PostgreSQL with database credentials.
MySQLWrite report rows into MySQL with database credentials.
SnowflakePush rows into Snowflake over HTTPS with a PAT token.
Databricks SQLLoad rows into Databricks SQL with a Personal Access Token.
Cloudflare R2Write report files to your R2 bucket with access keys.
Excel / CSVA Drive file you can open in Excel.
ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Review incident.io incidents, severity levels, and on-call rotation schedules.
3 closed standard incidents were logged this month (1 Major, 2 Minor) across 2 active on-call schedules.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
Start from a goal
Incidents
incident.io incidents with reference code, name, status category, severity, mode, and creation date.
Use this template →Severities
incident.io configured severity levels with rank and description.
Use this template →On-call schedules
incident.io on-call rotation schedules with timezone and creation date.
Use this template →incident.io incidents & schedules
Incidents, severity levels, and on-call rotation schedules.
Use this template →How it works
Create a project and choose incident.io in Data sources.
Pick where it goes. This one sends the numbers to Amazon Redshift.
Pick where it goes. Choose Incidents, Severities, or On-call schedules and a destination.
Sample report
| Incident ID | Reference | Incident name | Status category | Severity | Severity ID | Severity name | Rank |
|---|---|---|---|---|---|---|---|
| 1024 | INC-104 | Elevated API latency | closed | Minor | 1024 | 1,240 | 4.2 |
| 1025 | 640 | 640 | Pending | 640 | 1025 | 640 | 8.6 |
| 1031 | 210 | 210 | Refunded | 210 | 1031 | 210 | 12.1 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with incident.io
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.
incident.io + Search Console“Are search clicks and site visits moving together?”See Search Console →
incident.io + Shopify“Did more visits mean more orders this week?”See Shopify →
incident.io + Stripe“Did the traffic spike bring new paying customers?”See Stripe →
incident.io + HubSpot“Which weeks with more traffic also brought more deals?”See HubSpot →Questions
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 incident.io, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in incident.io. Read-only reporting access using your incident.io API key. Incidents and schedules are never modified.
This page lists 15 report fields across 3 datasets. You pick the columns when you build the report.
Incidents, severity levels, and on-call schedules from incident.io. Account permissions and the records available from the provider determine which rows can be read.
One for each incident.io 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.
Try incident.io with sample data first
Build the report first, then add incident.io when you are ready.