Linking xMatters (Everbridge) 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 xMatters (Everbridge) connector syncs events, people, groups, 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 xMatters instance subdomain and REST API credentials to pull your xMatters data.
Use HTTP Basic auth with a REST Web Service User (or an API key as the username and its secret as the password). The account needs read access to the resources you want to sync.
You'll be asked for:
- Company subdomain: for example
acme. - Username or API key
- Password or API key secret
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 xMatters (Everbridge) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Company subdomain | text | Yes |
Username or API key | text | Yes |
Password or API key secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
events | An alert (event) initiated in xMatters, including its status, priority, and timestamps. | Incremental, Full refresh | created | — |
people | A user in the xMatters instance who can be notified and can respond to events. | Full refresh | — | — |
groups | A group of recipients used to target and escalate notifications. | Full refresh | — | — |
devices | A contact method (device) belonging to a user, such as email, SMS, or push. | Full refresh | — | — |
sites | A physical or logical location that users can be associated with. | Full refresh | — | — |
roles | A role that defines the set of permissions a user has in xMatters. | Full refresh | — | — |
dynamic_teams | A team whose membership is derived dynamically from user attributes. | Full refresh | — | — |
plans | A communication plan that groups forms, integrations, and configuration used to initiate events. | Full refresh | — | — |
subscriptions | A subscription that notifies users when events matching its criteria are initiated. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the username or 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.