Connect DataDeveloper & APIs
PagerDuty
PagerDuty is in Preview in the connection wizard: it is built on PagerDuty’s documented API and has not yet been proven against a live account, so check the imported tables before relying on them.
-
In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.
-
Pick PagerDuty on that page (search or browse by category).
-
Fill in the connection details below, then test the connection and save.
Connection details
Section titled “Connection details”| Field | What to enter |
|---|---|
| Service region | api.pagerduty.com (US) or api.eu.pagerduty.com (EU). Default api.pagerduty.com. |
| API key | Integrations → API Access Keys → a read-only key. Stored encrypted and never shown again. |
Test Connection reads one page of records with these values; nothing is saved until you import.
Tables
Section titled “Tables”Pick the tables to import — each one becomes a table in the source:
| Table | What it holds |
|---|---|
incidents |
Incidents (last 12 months) — re-read in full on every refresh |
services |
Services |
users |
Users |
teams |
Teams |
escalation_policies |
Escalation policies |
schedules |
Schedules (not selected by default) |
Every table is read through all of its pages, nested fields become parent.child
columns, and the whole set is imported at once: the import’s row and size limits
count the picked tables together, and if they pass one, nothing is imported and
the message says which table and which limit. Refresh the source on a schedule,
or by hand, to re-read every table; a table that comes back empty is refused
rather than emptied unless you allow it. Nothing is ever written to PagerDuty.
The requests follow PagerDuty’s API reference.
Related
Section titled “Related”- Connector catalog — everything DataSquares connects to.
- Quickstart — from connection to shared dashboard.