Census

How to integrate Census with Webflow

What is Census? Census is a reverse ETL platform (now part of Fivetran) that syncs data from cloud data warehouses like Snowflake, BigQuery, Redshift, and Databricks into business applications using SQL queries. For Webflow, it pushes warehouse records into Webflow CMS collection items and keeps them current on a schedule you set.

The most direct way to connect the two is the Census app, which authorizes through OAuth. For workflows the app does not cover, such as cross-system orchestration or custom sync monitoring, you can also build against the Webflow and Census APIs directly.

Use the Census app

The Census app connects your data warehouse to Webflow and writes records into CMS collection items on a schedule you control. Set up the destination inside Census:

1. Open Destinations in Census and select New Destination.
2. Choose Webflow, then log in to authorize Census through OAuth and grant access to the sites you want to sync.
3. Create a sync that maps your warehouse columns to a Webflow collection’s fields, using the Slug field as the unique identifier.
4. Choose a sync behavior and set the schedule.

Census offers three sync behaviors for Webflow. Update or Create (upsert) adds new items and updates existing ones by matching on the slug field. Update Only modifies existing items without creating new ones, which suits content your team maintains by hand. Mirror makes Webflow match your source exactly, including deleting items that no longer appear in your query.

Mirror deletes Webflow items that are missing from your Census source, so a filtering error or an incomplete query can remove live content. Test Mirror against a staging collection before you run it in production.

Scheduling and field mapping

You decide how often syncs run and how fields line up. Schedule syncs from weekly down to continuous intervals, trigger them after dbt Cloud or Fivetran jobs finish, or start them programmatically through the Census API. When collections reference each other, sync sequences run the dependent syncs in order. The field mapper connects warehouse columns to collection fields and supports options like Set If Empty to avoid overwriting existing content, Liquid templating for transformations, and skipping null values. Before each run, Census validates the data, flags null values in required fields and duplicate slugs, skips records it cannot write, and reports failures in its interface.

Important limitations

Two Webflow constraints shape large syncs. Webflow caps a site at 10,000 CMS items across all collections combined, not per collection, so plan your data model to stay within it or move to a Webflow plan or add-on that raises the cap. Syncs also respect Webflow’s API rate limits of 60 requests per minute on Starter and Basic plans and 120 on CMS, eCommerce, and Business plans, so an initial sync of 5,000 items on a Basic plan can take over 83 minutes.

Build with the Webflow and Census APIs

For workflows the app does not cover, you can call the Census API and the Webflow Data API directly. The Census API runs at https://app.getcensus.com/api/v1 for US workspaces and https://app-eu.getcensus.com/api/v1 for the EU.

Monitor syncs with webhooks

Census posts webhook events so external systems can react the moment a sync finishes. It emits events including sync.started, sync.completed, sync.success, sync.failed, sync.triggered, sync.alert.raised, and sync.alert.resolved. Build middleware that consumes these events to update a status collection in Webflow, post Slack alerts, or invalidate a cache when content changes.

What you can build with Census Webflow integration

Pairing a warehouse with Webflow turns your CMS into a rendering layer for data you already model in SQL. A few patterns come up repeatedly once the sync is in place.

Teams most often build the following:

• Warehouse-driven content pages: Publish product, pricing, or location collections straight from warehouse tables, so those pages stay accurate without anyone editing items by hand.
• Scheduled content refreshes: Run syncs on a cadence to update existing items, keeping inventory counts, event details, and reported metrics current across every page that uses them.
• Enriched editorial content: Use Update Only syncs to layer warehouse fields onto items your writers create manually, adding structured data without overwriting their editorial work.
• Data-backed landing pages: Feed segmented audience data from your warehouse into collections that power targeted landing pages and personalized content blocks across the site.

Each pattern runs on the same pipeline from your warehouse to the CMS, so start with one collection and expand once a sync runs cleanly. To see exactly what Census writes into your collections, explore the CMS API guide.