> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking PagerDuty as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/pagerduty

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The PagerDuty connector pulls your PagerDuty incident and on-call data into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to PagerDuty.
3.  You need a PagerDuty REST API key. In your PagerDuty account, go to **Integrations → API Access Keys** and create a key, selecting the **Read-only** option — that's all this source needs.
4.  Back in PostHog, enter the key in the `API key` field and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using PagerDuty data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `incidents` | Incidents in your account | Incremental |
| `log_entries` | Log entries recording activity on incidents | Full refresh |
| `services` | Services that incidents are raised against | Full refresh |
| `users` | PagerDuty users | Full refresh |
| `teams` | Teams in your account | Full refresh |
| `escalation_policies` | Escalation policies | Full refresh |
| `schedules` | On-call schedules | Full refresh |
| `priorities` | Incident priorities | Full refresh |
| `vendors` | Integration vendors | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

Incremental sync on `incidents` filters on `created_at`, so it only picks up newly created incidents. Status changes to incidents created before the cursor are not re-fetched.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `incidents` | An incident representing a problem on a service that requires response. | Incremental, Full refresh | created\_at | — |
| `incident_alerts` | An alert grouped under an incident: one event from a monitoring tool, before de-duplication into the incident. | Full refresh | — | — |
| `log_entries` | A log entry recording an action or change on an incident (triggered, acknowledged, notified, etc.). | Full refresh | — | — |
| `change_events` | A change event, such as a deploy or a configuration change, sent to PagerDuty by an integration. | Full refresh | — | — |
| `services` | A service representing an application, component, or team monitored in PagerDuty. | Full refresh | — | — |
| `users` | A user account in the PagerDuty account. | Full refresh | — | — |
| `teams` | A team that groups users, services, and escalation policies in PagerDuty. | Full refresh | — | — |
| `team_members` | A membership row that joins a user to a team, with the user's role on that team. | Full refresh | — | — |
| `escalation_policies` | An ordered set of escalation rules that determine who is notified when an incident is not handled. | Full refresh | — | — |
| `schedules` | An on-call schedule defining which users are on call over time. | Full refresh | — | — |
| `oncalls` | An on-call entry: a user who is on call for a level of an escalation policy at the time of the sync. | Full refresh | — | — |
| `priorities` | A priority level that can be assigned to incidents to rank their importance. | Full refresh | — | — |
| `vendors` | A third-party vendor that integrates with PagerDuty (e.g. a monitoring tool). | Full refresh | — | — |