Source connector

Opsgenie connector

Opsgenie integration for databases, warehouses and BI tools

On-call alerting and incident escalation. Datrise captures Opsgenie entities such as alerts, incidents, schedules, escalations, teams and notification logs, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Opsgenie REST API v2 authenticates with API key, incremental runs key on updatedAt.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `opsgenie_alerts`) with a schema derived from the Opsgenie API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Opsgenie pipeline page, and join the waitlist to get the Opsgenie connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Opsgenie data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
alerts	opsgenie_alerts	Upsert by primary key, incremental on updated-at
incidents	opsgenie_incidents	Upsert by primary key, incremental on updated-at
schedules	opsgenie_schedules	Upsert by primary key, incremental on updated-at
escalations	opsgenie_escalations	Upsert by primary key, incremental on updated-at
teams	opsgenie_teams	Upsert by primary key, incremental on updated-at
notification logs	opsgenie_notification_logs	Append-only, incremental by timestamp

Opsgenie API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Opsgenie REST API v2
Authentication	API key — API integration key sent as an `Authorization: GenieKey <key>` header; the key's Configuration Access plus Read/Create-Update/Delete rights determine what it can call.
Pagination	offset — List Alerts takes `offset`/`limit` (default 20, max 100 per page) and returns `paging.next`/`first`/`last` URLs, but the sum of `offset` and `limit` cannot exceed 20,000.
Rate limit	Not published
Incremental cursor	updatedAt — The alert search query language supports range operators on `updatedAt` (e.g. `updatedAt>=...`), and `updatedAt` is also a valid `sort` field on List Alerts.
Webhooks	Yes — Webhook integration (Settings > Integrations > Webhook)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Opsgenie

List Alerts hard-caps retrieval at 20,000 records per query (`offset + limit` must stay under 20,000); a connector polling a high-volume account must narrow the search query (e.g. by time window) to stay under that ceiling rather than paging through everything.
Rate limits are not a fixed published number: each domain (Alert, Integration, Configuration, ...) gets a BaseLimit that is then multiplied by subscription plan and purchased user-seat count, so the safe request rate differs per account and must be read from the `X-RateLimit-State`/`X-RateLimit-Period-In-Sec` response headers rather than assumed.
Many write operations (bulk actions, some alert actions) return HTTP 202 immediately and must be polled via `GET /v2/alerts/requests/:requestId` to learn whether they actually succeeded.
There is no dedicated bulk-export or deleted-alerts endpoint; a connector must paginate `GET /v2/alerts` for full extracts and cannot detect deletions after the fact since deleted alerts simply stop appearing.

Compare this against every other documented API

Popular destinations for Opsgenie

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Opsgenie connector FAQ

What Opsgenie data does the connector extract?: 6 objects: alerts, incidents, schedules, escalations, teams and notification logs. Each lands in its own table with types preserved; history-style objects (1: notification logs) load as append-only streams.
Is the Opsgenie integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Opsgenie data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Opsgenie → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Opsgenie pipeline with guided onboarding

Join the waitlist to get priority access for Opsgenie integrations with guided setup, schema-aware mapping, and production-grade incremental sync.