Linking Zenduty as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Zenduty connector syncs teams, account members, incidents, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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.
Enter your Zenduty API key to automatically pull your Zenduty incident-management and on-call data.
Create an API key in your Zenduty account under Account Settings → Access → API Keys (account owners and admins only). The key is account-scoped and read access is enough for syncing.
You'll be asked for:
- API key
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_attimestamp). 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 for a full explanation of how each mode works and how to choose between them.
All Zenduty tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
teams | Teams in your Zenduty account. Each team owns its own services, escalation policies, schedules, and members. | Full refresh | — | — |
account_members | Members (users) of your Zenduty account, with their contact details and account role. | Full refresh | — | — |
incidents | Incidents across your Zenduty account, with their status, urgency, and timing — the basis for MTTR/MTTA and incident-volume analysis. | Full refresh | — | — |
services | Services within a team. Each service maps to an escalation policy that dictates how its incidents escalate. | Full refresh | — | — |
escalation_policies | Escalation policies for a team — the ordered rules (schedules and users) that decide who is notified as an incident escalates. | Full refresh | — | — |
schedules | On-call schedules for a team, defining rotations and who is on call at a given time. | Full refresh | — | — |
team_members | Membership rows linking users to a team, including their role within that team. | Full refresh | — | — |
roles | Incident roles defined for a team (e.g. incident commander, communications lead). | Full refresh | — | — |
postmortems | Post-incident retrospectives (postmortems) authored for a team's incidents. | Full refresh | — | — |
maintenance_windows | Scheduled maintenance windows for a team, during which alerting for affected services is suppressed. | Full refresh | — | — |
slas | Service-level agreements configured for a team, used to track response and resolution targets. | Full refresh | — | — |
tags | Tags defined for a team, used to categorize incidents and services. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.