Linking Perigon as a source
This source is currently in alpha. The interface and available tables may change.
The Perigon connector syncs news articles, story clusters, journalists, media sources, people, companies, and topics from the Perigon news intelligence API, so you can analyze news coverage and media data alongside your product data.
Prerequisites
You need a Perigon account with API access. The datasets you can sync depend on your Perigon plan, and tables outside your plan fail with a permission error.
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.
When linking Perigon, you'll need:
- API key – find it on your Perigon account dashboard after signing up and verifying your email.
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.
Articles and story clusters support incremental sync using Perigon's server-side date filters: articles sync by publication date (pubDate), and stories sync by last-update time (updatedAt), which also picks up clusters that received new articles. The reference tables (journalists, sources, people, companies, topics) sync as full refresh.
Perigon caps each search at 10,000 results. Incremental syncs on articles and stories catch up across runs because each sync continues from the last synced timestamp, but a single full refresh returns at most 10,000 rows per table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
articles | News articles enriched by Perigon with categories, entities, sentiment, and source metadata. | Incremental, Full refresh | pubDate | — |
stories | Story clusters that group related articles covering the same news event, with aggregate summaries and stats. | Incremental, Full refresh | updatedAt | — |
journalists | Journalist profiles tracked by Perigon, with beats, outlets, and social links. | Full refresh | — | — |
sources | Media sources monitored by Perigon, with reach, bias, and paywall metadata. | Full refresh | — | — |
people | Public figures tracked by Perigon for entity matching in news coverage, keyed by Wikidata id. | Full refresh | — | — |
companies | Companies tracked by Perigon for entity matching in news coverage, with identifiers and firmographics. | Full refresh | — | — |
topics | Topics Perigon assigns to articles and stories, usable as filters in article search. | Full refresh | — | — |
Troubleshooting
- Your Perigon API key is invalid or has been revoked: generate a new key on your Perigon account dashboard, then reconnect the source.
- Your Perigon plan does not include access to this dataset: deselect the failing table in the source's schema settings, or upgrade your Perigon plan.
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.