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

# Linking Opsgenie as a source

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

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

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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 Opsgenie connector pulls your Opsgenie alerting and on-call data – alerts, incidents, users, teams, schedules, escalations, services, and integrations – into the PostHog data warehouse.

**Opsgenie end of support**

Atlassian has announced [end of support for Opsgenie](https://support.atlassian.com/opsgenie/docs/important-update-opsgenie-end-of-support-announcement/). Opsgenie APIs are scheduled to shut down on April 5, 2027, after which this source will stop syncing.

## Prerequisites

You need an Opsgenie API key with **Read** access. The `integrations` table additionally requires **Configuration access**. You can create a key in Opsgenie under **Settings → API key management**.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Opsgenie, you need to provide:

1.  Your Opsgenie **API key** from **Settings → API key management**.
2.  Your Opsgenie **region** – US (`api.opsgenie.com`) or EU (`api.eu.opsgenie.com`), matching the region your Opsgenie account is hosted in.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The `alerts` and `incidents` tables support incremental sync on `createdAt`. Opsgenie's search API can only filter on creation time, so incremental syncs pick up newly created rows but not later status changes to existing rows – run a periodic full refresh if you need those reflected.

## Configuration

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

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `alerts` | An alert created in Opsgenie by an integration, the API, or a user, representing an event that may need attention. | Incremental, Full refresh | createdAt | — |
| `incidents` | An incident representing a service outage or degradation that requires coordinated response. | Incremental, Full refresh | createdAt | — |
| `users` | A user account in the Opsgenie organization. | Full refresh | — | — |
| `teams` | A team that owns alerts, services, and on-call schedules. | Full refresh | — | — |
| `schedules` | An on-call schedule defining who is on call and when. | Full refresh | — | — |
| `escalations` | An escalation policy describing how unacknowledged alerts are escalated. | Full refresh | — | — |
| `services` | A business service used to track incident impact. | Full refresh | — | — |
| `integrations` | An integration that creates alerts in Opsgenie (e.g. a monitoring tool or email integration). | Full refresh | — | — |

## Troubleshooting

If the source fails to connect, check that the API key was created under **Settings → API key management** (not an integration-specific key), that it has **Read** access, and that the selected region matches your Opsgenie account.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.