Clay

Using Clay with Webflow lets teams turn a static site into a data-driven workflow for lead enrichment, personalized pages, and CMS updates.

Webflow handles site design, hosting, and content management well. But it has no built-in way to enrich form submissions with company data like industry, employee count, and revenue. It also cannot, on its own, orchestrate account-specific landing page generation or keep content management system (CMS) collections updated with live company intelligence from external data sources. Teams that need data-driven personalization or lead enrichment hit a wall quickly.

Clay fills that gap by connecting 150+ data providers to Webflow workflows and CMS collections from within Clay. Form submissions become enriched lead records, company data populates personalized account-based marketing (ABM) pages, and CMS collections stay current without manual updates. Together, the two tools let teams use a Webflow site as an active component in their go-to-market workflow. Webflow hosts a Clay detail page, but setup starts in Clay rather than through a traditional installable Webflow Designer app.

This integration is most useful for growth teams running account-based campaigns, RevOps leads routing inbound submissions, marketing ops managers maintaining data-driven sites, and agencies managing CMS content across client projects. Each of these roles benefits from automated data enrichment that connects form captures or CMS records to live company intelligence without manual research.

How to integrate Clay with Webflow

What is Clay? Clay is a go-to-market (GTM) data enrichment and workflow automation platform. It connects over 150 third-party data providers into a single spreadsheet-like interface. It supports waterfall enrichment — cascading through multiple providers until a result is found — along with an AI research agent called Claygent for custom data lookups. Clay also includes a built-in email sequencer and integrations with CRMs, ad platforms, and outbound tools.

Teams combine Clay and Webflow when they need to move enriched data into website content. They also use the pairing to capture website interactions as inputs for enrichment workflows. A demand gen team might generate hundreds of personalized ABM landing pages from Clay data pushed into Webflow CMS collections. A RevOps team might route Webflow form submissions into Clay for scoring and enrichment before sending qualified leads to a CRM.

The Clay-Webflow integration supports 4 approaches:

• Clay's native Webflow integration in Clay handles CMS item creation, retrieval, updates, and personalized landing page generation without code.
• Webflow form webhooks let you send form submission data directly into Clay tables for enrichment.
• Zapier connects Webflow triggers to Clay actions through pre-built templates and custom workflows.
• The Webflow Data API and Clay's HTTP API tool give you full control over CMS writes, webhook subscriptions, and bidirectional data flows. They require server-side configuration.

Most implementations combine two or more of these methods. The choice depends on whether the primary data flow is inbound (Webflow to Clay) or outbound (Clay to Webflow).

Use Clay's native Webflow integration

Clay's built-in Webflow integration lets you create, read, and update Webflow CMS collection items directly from a Clay table. It also includes a dedicated action for generating personalized landing pages from enriched data. This is the primary no-code method for pushing enriched data from Clay into Webflow. Webflow also hosts a Clay Webflow app detail page, but the integration itself is initiated from within Clay and uses OAuth (open authorization) authentication, where you authorize Clay to access your Webflow account. Connect your Webflow account from within Clay's interface.

[image placeholder]

To set up the integration:

1. Open a Clay table and click Add enrichment.
2. Search for Webflow and select one of the available actions under Integrations.
3. Click Select Webflow account, then + Add account to authenticate via OAuth with your Webflow credentials.
4. Choose your target site and CMS collection.
5. Map Clay table columns to Webflow CMS fields. For the "Create Collection Item" action, specify whether items should be created as drafts or published.
6. Run the enrichment to push data from Clay into Webflow.

Once the mapping is complete, Clay can start writing enriched records into the Webflow collection you selected.

The four native actions cover distinct use cases:

• Create Collection Item adds new items to a specified Webflow CMS collection
• Get Collection Item retrieves a single item from a collection for use in Clay enrichment workflows
• Update Collection Item modifies an existing item's field values
• Generate Personalized Landing Page creates new pages using company or contact data, including brand colors, logos, and AI-written value propositions

These actions cover both standard CMS sync and account-specific page generation inside Clay's Webflow integration.

A few things to know before running the integration. Webflow requires custom CMS fields to have at least one published value before API access. Publish your collection with sample data first. Slugs must use lowercase letters and hyphens only (e.g., company-overview, not Company_Overview). When updating a collection item, any field you omit in the mapping resets to its default value. Map every field you want to keep. Image fields require direct, CORS-enabled (cross-origin resource sharing) URLs.

Send Webflow form data to Clay via webhooks

The native integration handles Clay-to-Webflow data flow. For the reverse direction like capturing Webflow form submissions and sending them to Clay, webhooks are the most direct approach. Every Clay table can generate a unique inbound webhook URL. This URL accepts HTTP POST requests with JSON payloads. Webflow can send form data to that endpoint.

There are two ways to connect a Webflow form to a Clay webhook. They behave differently.

Use the form action field

This approach sends form data directly to Clay by overriding the form's default submission behavior. It requires only a copy-paste of the webhook URL.

To connect a Webflow form to Clay via the action field:

1. In Clay, create a new table, click + Add at the bottom of the workbook, search for Webhooks, and select Monitor webhook. Copy the generated webhook URL.
2. In Webflow, select your form element. Locate the Action field in the right-side settings panel and paste the Clay webhook URL.
3. Publish your Webflow site and submit a test form entry. Verify the data appears as a new row in your Clay table.

When a custom action URL is set, form submissions go directly to Clay. They are not stored in Webflow's form submissions panel. If you need submissions saved in both locations, use the site settings webhook method instead.

Use the site settings webhook

This approach keeps Webflow's native form handling intact while also sending data to Clay. Submissions are stored in Webflow and forwarded to Clay simultaneously.

To set up a webhook in site settings:

1. In Clay, create a table with a webhook source and copy the generated URL.
2. In Webflow, go to Site settings > Integrations > Webhooks.
3. Click Add Webhook, select Form Submission as the trigger type, and paste the Clay webhook URL.
4. Copy the unique secret key that appears. Webflow displays this key only once. Store it immediately.
5. Click Hide key forever to confirm, then publish your site.
6. Submit a test form to verify data arrives in your Clay table.

Webflow webhooks retry failed deliveries a limited number of times. After repeated failures, Webflow auto-deactivates the webhook and sends an email notification. If your Clay endpoint is unavailable during the retry window, Webflow may deactivate the webhook permanently. Contact Webflow support to reactivate it. For production workflows where you need to verify webhook authenticity, register webhooks via the Webflow API rather than the dashboard. Only API-created webhooks include HMAC (hash-based message authentication code) signature headers.

Connect Clay and Webflow with Zapier

Zapier provides a direct Clay + Webflow integration with pre-built triggers and actions for both platforms. This requires the least configuration to build workflows without touching webhooks or API setup. Zapier works well for teams that want to route Webflow form submissions into Clay for enrichment. It also supports syncing Clay records back to Webflow CMS collections through Webflow actions in a visual interface.

Zapier supports the following Webflow triggers for Clay workflows:

• New Form Submission (instant) creates a record in a Clay table whenever someone submits a Webflow form
• New Order (instant) sends e-commerce order data to Clay for enrichment
• Updated Order (instant) pushes order status changes to Clay

These triggers cover the main Webflow events most teams would route into Clay through Zapier.

Zapier's Clay actions include:

• Create Record in Table adds a new row to a Clay table
• Update Record in Table modifies an existing Clay record
• Find Row in Table searches for a matching record before creating or updating

These actions make Zapier a practical option for simple Webflow-to-Clay automations without direct webhook or API setup.

A pre-built template called "Create new Clay records from Webflow form submissions" handles the most common use case with minimal configuration. Zapier also supports the reverse direction — mapping Clay data into Webflow CMS items via Webflow's Create Item and Update Item actions. For workflows that need form data stored in Webflow and simultaneously sent to Clay, Zapier avoids the tradeoff between the form action field method and the site settings webhook method. It handles both destinations in a single automation.

Build with the Webflow Data API and Clay's HTTP API tool

For full control over data flow, use Clay's HTTP API tool to call Webflow's Data API directly. This approach requires configuring API authentication, endpoint URLs, and request bodies within Clay's enrichment column system. It suits teams that need custom field mapping, conditional publishing logic, or workflows beyond what the native integration supports.

The relevant APIs are:

• Webflow's Data API v2 handles CMS collection reads and writes, form submission retrieval, site publishing, and webhook management
• Clay's HTTP API tool acts as an outbound HTTP client embedded in Clay's enrichment columns. It can call any REST endpoint with configurable methods, headers, and JSON bodies.
• Webflow webhooks trigger real-time events for form submissions, CMS item changes, and site publishes. These can target Clay's inbound webhook URLs.

Clay does not expose a traditional REST API for external queries. Data enters Clay via inbound webhooks. Clay sends data outward through its HTTP API enrichment columns on a per-row basis.

Push enriched data to Webflow CMS collections

This is the most common API-level pattern. Clay enriches rows in a table, then an HTTP API column fires a request to Webflow's CMS endpoint for each row.

To configure Clay's HTTP API tool for Webflow CMS writes:

1. In your Clay table, add a new column and select HTTP API enrichment.
2. Set the HTTP method to POST (for new items) or PATCH (for updates). Enter the endpoint URL: https://api.webflow.com/v2/collections/{collection_id}/items for creates, or https://api.webflow.com/v2/collections/{collection_id}/items/{item_id} for updates.
3. Under Headers, add Authorization: Bearer <your_webflow_token> and Content-Type: application/json. Save the authorization header at the workspace level using Clay's HTTP API (Headers) account feature so it is reusable across columns.
4. In the JSON body, map Clay column references to Webflow CMS field slugs. String values need quotation marks around the column reference (e.g., "/Company Name"). Number values do not (e.g., /Employee Count).
5. Configure Clay's rate limiter to control request frequency. Clay fires requests at full speed by default. Set a limit appropriate for your Webflow plan to avoid failed requests.
6. Optionally, add a second HTTP API column that calls POST https://api.webflow.com/v2/sites/{site_id}/publish to make changes live. Batch all CMS writes before triggering a publish to avoid failed requests.

Creating items via the API always produces drafts — even through /live endpoint paths. A separate publish step is required for new items. When updating existing items via the /live endpoints, both the staged and live versions update simultaneously. Also note that Clay's HTTP API Source mode does not support pagination. Only the first 100 items are returned per request.

Subscribe to Webflow CMS events

For workflows triggered by CMS changes — such as enriching newly created collection items — register a Webflow webhook that targets your Clay table's inbound URL.

To register a CMS event webhook:

1. Generate an inbound webhook URL from your Clay table.
2. Send a POST request to https://api.webflow.com/v2/sites/{site_id}/webhooks with the triggerType set to collection_item_created and the url set to your Clay webhook URL. This requires the sites:write scope on your Webflow API token.
3. Webflow will send a JSON payload to Clay whenever a new CMS item is created. The payload includes the item's id, collectionId, fieldData, and draft status.

Be aware of the infinite loop risk documented in Clay's official guidance. If a collection_item_changed webhook triggers Clay enrichment, and Clay writes the enriched data back to the same Webflow collection item, Webflow fires another collection_item_changed event. This creates a continuous loop. Break this cycle by using a separate collection for Clay output, adding a flag field that Clay checks before processing, or limiting webhook triggers to collection_item_created instead of collection_item_changed.

What can you build with the Clay Webflow integration?

Integrating Clay with Webflow lets you connect enriched data to CMS-driven pages. You avoid rebuilding content manually for every new campaign or account.

• Account-based landing pages at scale: Generate hundreds of personalized landing pages for ABM campaigns. Each page is populated with the target company's logo, brand colors, industry-specific messaging, and tailored CTAs. Verkada uses this approach to create outbound campaign pages that previously required manual design work for each account.
• Inbound lead enrichment pipelines: Capture form submissions from a Webflow contact or demo request form. Route them to Clay for waterfall enrichment across 150+ data providers. Write the enriched records back to a Webflow CMS collection or downstream CRM. A RevOps team can score and route leads before they touch Salesforce, filtering out unqualified submissions automatically.
• Dynamic company and partner directories: Build CMS-powered directory pages on Webflow — partner listings, customer showcases, or vendor marketplaces. Clay populates and keeps these current with enriched company data including employee counts, funding status, and technology stacks. Each directory entry links to a CMS-generated detail page rendered through a Collection List.
• Real-time content updates from live data: Use Clay's scheduling feature to periodically re-enrich CMS collection items with fresh data. Updated customer counts, recent funding rounds, or new case studies flow in so your Webflow site reflects current information without manual publishing cycles.

If you need more control over conditional publishing logic, multi-step enrichment chains, or webhook-driven CMS updates, the API integration path covers those cases with full flexibility.