What does a Clay website integration do?
A Clay website integration turns a short form submission into a full lead record. The website sends the form data to a Clay table through a webhook, Clay runs enrichment columns on each new row, and the finished record goes wherever your team works. Clay's docs describe every table's webhook as processing data as soon as it arrives.
Visitor submits
The form asks for a work email and perhaps one qualifying question.
Webhook to Clay
The site sends the email, form answers, UTMs and page URL to a Clay table.
Enrich
Clay columns look up the company, size, industry and the person's role from the providers you've set up.
Score and route
Formulas or AI columns score fit and decide where the lead goes.
Push out
The record is sent to your CRM, a Slack channel or an outbound sequence.
The website's part is small but easy to get wrong: a form that always sends the same fields, a secure request to the right table, and a thank-you state that doesn't wait for enrichment to finish. Clay's table design and enrichment choices are usually owned by your growth or RevOps team.
Can enrichment let you shorten your website forms?
Yes, and that's the main reason to wire Clay into a website. If Clay can find the company, headcount and job title from a work email, the form doesn't need to ask for them. Fewer fields means less effort for the visitor, though the trade-offs are real.
Pros
- Forms can drop to an email and one question that enrichment can't answer
- Sales sees company and role on every lead, not only on the ones that filled in every field
- Scoring happens before the lead reaches the CRM, so reps start with the best fits
- Enrichment rules change in Clay without a website release
Cons
- Enrichment misses some records, especially personal emails and very small companies
- Each enrichment uses Clay credits, so spam and junk submissions cost money
- Data from providers can be stale or wrong, so reps still need to check before acting on it
- Collecting less and enriching more raises privacy questions you need to answer in your notice
We keep one or two fields enrichment can't infer, such as what the visitor wants help with. Our guide to landing page form design covers which fields earn their place.
How does Clay connect to Webflow, Framer and Next.js forms?
Clay receives data through a webhook URL from a table, so any form that can send an HTTP request, directly or through an automation tool, can feed it. The difference between platforms is whether the request can be sent securely and with all the data you need.
Task | Webflow | Framer | Next.js |
|---|---|---|---|
Send form data to Clay | Via Webflow's form webhooks or an automation tool, check current options | Via Framer's form destinations or an automation tool, check current options | Server route posting to the Clay webhook |
Keep the auth token secret | Only through a server or automation in between | Only through a server or automation in between | Stored as a server environment variable |
Send UTMs and page URL | Hidden fields filled by a script | Hidden fields or a code component | Added on the server from stored values |
Spam filtering before Clay | Platform spam protection | Platform spam protection | Custom validation and bot checks |
Send to CRM and Clay at once | Automation tool fans out | Automation tool fans out | One server route sends to both |
On Next.js we post the form to our own server route, which validates it, sends it to the CRM and forwards it to Clay with the token in the header. On Webflow and Framer, an automation tool usually sits in between, which our Zapier integration page covers. Our guide to forms and integrations on Next.js marketing sites shows the server pattern.
What limits and pitfalls should you plan for with Clay webhooks?
Plan for Clay's documented webhook limits, duplicate rows and junk submissions before launch. Clay's docs say a webhook source stops accepting data after 50,000 submissions, deleting rows doesn't reset that count, and outside Enterprise plans with auto-delete you have to create a new webhook. A high-traffic form can reach that without anyone noticing.
- Silent stop at the limit: submissions stop arriving in Clay. We note the webhook's start date and set a reminder to check the count.
- Token in the browser: Clay's optional auth token goes in the request header, and Clay shows it only once. If it's in front-end code, anyone can post to your table.
- Duplicates: retries and double clicks create repeat rows, so we dedupe on email before enrichment runs.
- Spam using credits: bots trigger enrichment you pay for. Filter before the webhook, not after.
- Waiting on enrichment: a thank-you page that waits for Clay feels broken. Confirm the submission at once and enrich in the background.
- Two sources of truth: the CRM and Clay disagree on a lead. Decide which system writes which fields.
What happens to the lead after Clay enriches it?
After enrichment, the lead should go to the one place your team acts on it, with a clear owner. Clay can push records to CRMs such as HubSpot and Salesforce, post to Slack, or call any HTTP endpoint, so the routing is set up in Clay rather than in the website.
- Strong fit: create or update the CRM contact, assign an owner and post an alert in a sales channel.
- Medium fit: add to a nurture list with the enriched fields attached.
- Poor fit or no match: keep the record, skip the alert and let marketing review it.
- Existing customer: send it to the account owner or support instead of sales.
Hypothetical example: a two-field demo form
For example, suppose a developer-tools startup cuts its demo form to work email and 'What are you trying to solve?'. Clay looks up the company and the person's role. Engineering leaders at companies above the startup's target size are sent to the CRM with an owner and a Slack alert. Individual developers get an email pointing to the free tier. The form would go from seven fields to two, and sales would still see company, size and role on enriched leads. This is an illustration of the process, not a client result.
If you want visitors to book straight after submitting, pair this with our Chili Piper integration, and see our HubSpot integration page for the CRM side.
How do we set up Clay on your site, and what does it cost?
We start with the form and the data contract: which fields the site sends, in what format, and which system owns each field afterwards. Then we design the forms, build the connection, run test submissions through spam checks, the webhook and your CRM, and hand over a note listing the webhook, its token location and its submission limit.
Clay setup on the website side is part of our website package, $8,000 fixed for up to six pages including copy, design and the build. You'll need your own Clay account, and enrichment credits are billed by Clay, so check their current plans. We designed and built the site for ATQ Leads, a marketing business. Our guide to conversion tracking for lead-gen websites covers measuring what happens next. The next step is a free 30-minute call.

















