- Source
- Engineering Analytics
- Alpha
Move Pagerduty data anywhere it matters.
Send Pagerduty incidents, incident log entries and priorities to any warehouse, lake or AI app.
Source
Pagerduty
Snowflake
BigQuery
Postgres
Databricks
Claude
- Streams
- 4
- Destinations
- 50+
- Standard support
- 0.3.48
Overview
What is the Airbyte Pagerduty connector?
The Airbyte Pagerduty connector extracts data from Pagerduty and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes 4 streams you can select per connection.
- 01
Sync to your warehouse
Land 4 Pagerduty tables in 50+ destinations on a schedule you control.
- 02
Incremental syncs
Pull only the records that changed since the last run instead of reloading everything.
- 03
One authorization
Authenticate Pagerduty once and Airbyte keeps every scheduled sync running on it.
- 04
Cloud or self-hosted
Run the Pagerduty connector on Cloud, OSS, Hybrid.
4 streams
Every table you can sync from Pagerduty
Incidents Sync modes FullIncr. Incident Log Entries Sync modes FullIncr. Priorities Sync modes FullIncr. Users Sync modes FullIncr.
Setup
Live in eight steps
Begin by navigating to the Airbyte dashboard and selecting the "Sources" tab.
Click on the "Add Source" button and select "PagerDuty" from the list of available connectors.
Enter a name for your PagerDuty source and click "Next".
In the "Authentication" section, enter your PagerDuty API key and subdomain.
Click "Test Connection" to ensure that the credentials are correct and the connection is successful.
In the "Configure Schema" section, select the data you want to replicate from PagerDuty.
Click "Create Source" to save your configuration and begin syncing data from PagerDuty to your destination.
You can monitor the status of your source connector on the Airbyte dashboard and make any necessary changes to your configuration as needed.
Configuration fields
| Field | Type | Description |
|---|---|---|
| token* | string | API key for PagerDuty API authentication |
| cutoff_days | integer | Fetch pipelines updated in the last number of days |
| default_severity | string | A default severity category if not present |
| exclude_services | array | List of PagerDuty service names to ignore incidents from. If not set, all incidents will be pulled. |
| incident_log_entries_overview | boolean | If true, will return a subset of log entries that show only the most important changes to the incident. |
| max_retries | integer | Maximum number of PagerDuty API request retries to perform upon connection errors. The source will pause for an exponentially increasing number of seconds before retrying. |
| page_size | integer | page size to use when querying PagerDuty API |
| service_details | array | List of PagerDuty service additional details to include. |
Hybrid deployment
Sovereign by architecture, not by policy.
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
- Cloud
- OSS
- Hybrid
Your environment
Airbyte control plane
Related connectors
FAQ
Pagerduty connector questions
What data can I sync from Pagerduty with Airbyte?
4 streams: Incidents, Incident Log Entries, Priorities, Users.
Does the Pagerduty connector support incremental sync?
Yes. The Pagerduty connector supports incremental sync on selected streams, and full refresh on every stream.
Where can I run the Pagerduty connector?
Run the Pagerduty connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Start syncing Pagerduty in minutes.
Free 14-day trial. No credit card needed.