Linking Framer 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.
Contents
This source is currently in alpha. The interface and available tables may change.
The Framer connector syncs project, pages, collections, 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.
Sync your Framer site's pages, CMS collections and items, locales, redirects, and deployments.
Create an API key in your Framer project under Site Settings → General, then paste your project URL (https://framer.com/projects/...) and the API key. API keys are project-specific, so add one source per project.
You'll be asked for:
- Project URL or ID: for example
https://framer.com/projects/.... - 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 Framer tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Project URL or ID | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Project | The Framer project (site), including its current production and staging publish state. | Full refresh | — | — |
Pages | Web pages in the project's site tree. | Full refresh | — | — |
Collections | CMS collections in the project, with their field definitions. | Full refresh | — | — |
CollectionItems | Items (entries) across every CMS collection in the project. | Full refresh | — | — |
Locales | Locales configured for the project's localization. | Full refresh | — | — |
Redirects | URL redirects configured on the site. | Full refresh | — | — |
Deployments | Deployments (publishes) of the site on the active branch, newest first. | 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.