Sanity with Webflow
Sanity with Webflow
This one is for a specific shape of team: content lives in Sanity because the product needs it there too, but the marketing site should stay something marketing can edit. Sanity keeps the content, Webflow keeps the site, and a sync keeps them honest.
CMS work like this usually takes 1–2 weeks
What the integration covers
What syncs, and what needs a decision.
Wired up
- Sanity documents into Webflow collections, on publish rather than on a timer
- Portable Text converted to the rich text Webflow's CMS actually accepts
- References resolved in order, because Webflow needs the target published first
- Assets re-hosted on Webflow rather than hot-linked from Sanity's CDN
- Deletes and unpublishes propagated, so nothing outlives its source
Flagged upfront
- Webflow's CMS caps at 20,000 items and 40 collections on the Premium plan, so a large Sanity dataset is filtered rather than mirrored whole
- Portable Text is structured data and Webflow rich text is HTML, so the conversion is a build decision, not a field mapping
- Webflow publishes at most once a minute and its API is rate limited, so a bulk sync is paced rather than fired
- Two editing surfaces means one has to win; if Sanity is the source, the Designer stops being where content changes
The honest framing is that this is not a migration. Sanity stays where it is, keeps its schema and its editing experience, and Webflow becomes a rendering surface with a copy of the content. If the goal is to leave Sanity, this is not that project.
Two things decide whether the sync stays simple. Portable Text is Sanity’s structured representation of rich content, and Webflow’s CMS wants HTML — so somebody has to decide what a custom block becomes on the way across, and that decision is code, not configuration. And Webflow’s reference fields need the item being pointed at to exist and be published already, which forces the sync into passes rather than one loop.
Where this works well is a team that already treats Sanity as infrastructure. Where it works badly is a team hoping to edit in both places.
Other integrations
Wire up something else?
-
Google Analytics with Webflow
Analytics · typically 2–4 days
Learn more → -
Salesforce with Webflow
CRM · typically 3–5 days
Learn more → -
HubSpot with Webflow
CRM · typically 2–4 days
Learn more → -
Stripe with Webflow
Payments · typically 1–2 weeks
Learn more → -
Segment with Webflow
Data · typically 3–6 days
Learn more → -
Slack with Webflow
Comms · typically 1–2 days
Learn more → -
Intercom with Webflow
Support · typically 2–4 days
Learn more → -
Calendly with Webflow
Scheduling · typically 1–3 days
Learn more → -
Airtable with Webflow
Data · typically 3–6 days
Learn more → -
Pipedrive with Webflow
CRM · typically 2–4 days
Learn more → -
Shopify with Webflow
Ecommerce · typically 1–2 weeks
Learn more → -
Zapier with Webflow
Automation · typically 1–3 days
Learn more → -
Make with Webflow
Automation · typically 2–5 days
Learn more → -
Mailchimp with Webflow
Email · typically 1–2 days
Learn more → -
Typeform with Webflow
Forms · typically 1–2 days
Learn more → -
Memberstack with Webflow
Memberships · typically 1–2 weeks
Learn more → -
Finsweet Attributes with Webflow
Webflow · typically 1–4 days
Learn more → -
GSAP with Webflow
Interactions · typically 3 days–2 weeks
Learn more → -
Figma with Webflow
Design · typically Scoped with the build
Learn more → -
Google Maps with Webflow
Content · typically 2–5 days
Learn more → -
PostHog with Webflow
Analytics · typically 2–4 days
Learn more → -
Amplitude with Webflow
Analytics · typically 2–4 days
Learn more → -
Zendesk with Webflow
Support · typically 2–4 days
Learn more →
Reach out and see if we are a good fit.
Currently booking two to four weeks out.