Linking Nager.Date 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 Nager.Date connector syncs countries, country info, public holidays, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
None. The Nager.Date API is public, so no account or API key is needed.
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.
Pull public holiday data from the free Nager.Date API.
The API is open, so no credentials are required. Enter the ISO 3166-1 alpha-2 country codes you want to track, one per line or comma separated. For example:
A holidays table like this is commonly joined against event, order, or traffic timestamps by date and country to explain dips and seasonality.
The API only serves a rolling window of years around today, and it has no "changed since" filter, so every table syncs as a full refresh on each run. This also picks up holiday corrections the source publishes after the fact.
You'll be asked for:
- Country codes: for example
US GB DE.
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 Nager.Date tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Country codes | textarea | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Countries | Countries the Nager.Date API publishes public holiday data for. | Full refresh | — | — |
CountryInfo | Country names and region for each configured country, with bordering countries. | Full refresh | — | — |
PublicHolidays | Public holidays for each configured country, for the years the API currently supports. | Full refresh | — | — |
NextPublicHolidays | The next public holidays occurring within 365 days for each configured country. | 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.