← Back to Home
Webflow logo

Webflow

CMS

No-code website builder and CMS.

About Webflow

Webflow allows designers to build professional sites without code. The challenge is connecting those beautiful forms to your backend data. Integrating Webflow allows you to pipe leads directly into your CRM or dynamically update blog content from an external database like Airtable, bridging the gap between design and data.

Integration Capabilities

Webflow has 4 native integrations in its API directory. This page focuses only on guides we publish and maintain.

How Webflow Integrations Usually Work

Start with the implementation model, not the connector. We map each pair by intent so you can decide if native sync is enough or if this workflow needs stronger controls.

Webflow Integrations

8

Focused pages with known intent and use-case data.

Direct Paths

2

Native in at least one direction.

Connector Paths

6

Usually require mapping, retries, or approval gates.

Most Webflow integrations are built for Standard setup use cases. Open any guide below to see the recommended setup path and cost estimate.

Common Integration Patterns

  • - Headless CMS: Managing content in Airtable or Notion and syncing it to Webflow CMS collections for publishing.
  • - Lead Routing: Using native forms but sending the data via Logic/Make to HubSpot or Salesforce for complex lead scoring.
  • - Membership Gating: Integrating with tools like Memberstack or Outseta to gate content based on payment status in Stripe.

Integration Challenges

  • - CMS Item Limits: Webflow has strict limits on CMS items (e.g., 10k items on CMS plan). Large programmatic SEO projects often hit this wall.
  • - Form ID Changes: If you unpublish/republish or duplicate a project, Form IDs can change, breaking webhook connections.
  • - Rich Text Formatting: Syncing rich text from external databases (like Markdown in Airtable) to Webflow Rich Text fields often requires HTML conversion.

Before You Integrate

  1. 1. Map Reference Fields: If syncing multi-reference fields (e.g. 'Tags'), ensure the reference items exist in Webflow *before* syncing the main item.
  2. 2. Validate Image URLs: Webflow requires images to be hosted on a public URL to import via API.
  3. 3. Set Publish Status: Decide if the integration should set items to 'Draft' or 'Published' automatically.

Native Integrations from Webflow (2)

These guides cover integrations where Webflow includes a direct native path.

Connector-Based Integrations (6)

These workflows usually need connector logic. Open each setup guide to confirm scope before choosing a platform. If you need a starting point, use the recommendations in the section above.

Webflow — Common Questions

What does Webflow integrate with natively?

Webflow's marketplace includes Mailchimp, ActiveCampaign, Klaviyo, HubSpot, Salesforce, Google Analytics, Stripe (via the e-commerce module), Memberstack, and most major form/email tools. For e-commerce, Webflow's native store has integrations with Stripe, PayPal, Shippo, and ShipStation.

Does Webflow have an API for custom integrations?

Yes. Webflow's CMS API covers collections (Webflow's term for content types), items, and assets. The Forms API lets you receive submissions to a custom endpoint. Webhooks fire on form submissions, collection item changes, and e-commerce events. For low-code use Make or n8n.

How do I populate a Webflow CMS collection from Google Sheets or Airtable?

Common pattern for content-managed sites: editors update a Google Sheet or Airtable base, Make watches for changes and creates/updates the matching Webflow CMS item via API. Useful for blog posts, team directories, product catalogs, and event listings. After write, trigger a Webflow publish via the API so the change goes live.

How do I send Webflow form submissions to my CRM or notification tool?

Use Webflow's form webhook to point at Make. Route the payload to your CRM (HubSpot, Salesforce, Pipedrive), post to Slack #new-leads, append to a Google Sheet, and fire to your email tool. For multi-tenant marketing pages with different forms going to different teams, the router pattern in Make scales cleanly.