Docs / Data sources / Framer

Framer

Business software

Built when you ask for it

Sync Framer CMS collection data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Framer connector syncs your site's CMS data into analytics-ready tables in your data warehouse. Pull collections and collection items from the Framer Server API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Collections
  • Collection items

How it gets built

  1. Choose Framer when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Framer's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Framer itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (Bearer, project-scoped). Generate the key yourself under the target site's Site Settings > General tab; this API is still in open beta and scoped to one project per key.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Framer connector?
Not as a finished connector yet. Ingest builds it from Framer's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Framer data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Framer API documentation: https://www.framer.com/developers/server-api-introduction

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Framer