Linking New York Times 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 New York Times connector syncs article search, most popular viewed, most popular emailed, 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 New York Times API key to pull New York Times content.
Create a free developer account and register an app at the NYT Developer Network, then enable the APIs you want to sync (Article Search, Most Popular, Top Stories) on your app to get an API key.
Note: NYT enforces tight rate limits (≈10 requests/minute, 4,000/day), so syncs - especially Article Search - are intentionally throttled.
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.
Some New York Times tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Article Search query (optional) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
article_search | Articles matching a query and/or date window from the NYT Article Search API. Windowed by publication date and capped at 1000 results per query. | Incremental, Full refresh | pub_date | _id |
most_popular_viewed | The most viewed New York Times articles over the last 7 days. Point-in-time snapshot. | Full refresh | — | uri |
most_popular_emailed | The most emailed New York Times articles over the last 7 days. Point-in-time snapshot. | Full refresh | — | uri |
most_popular_shared | The most shared New York Times articles over the last 7 days. Point-in-time snapshot. | Full refresh | — | uri |
top_stories | The current top stories on the New York Times home section. Point-in-time snapshot. | Full refresh | — | uri |
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.