// website builders and cms
Via APIWebflow email verification with pingutil
Native Webflow forms accept whatever is typed, so fake and mistyped addresses land in your submissions and in whatever tool you forward them to. Webflow cannot run your code before a submission is stored, so the fix happens one step later: a form_submission webhook sends each submission to your endpoint, which verifies the email with pingutil and forwards only the addresses worth keeping.
Where it connects: Webflow Data API webhook, form_submission trigger
What goes wrong without it
- Our Webflow contact form fills up with test@test.com and temp-mail addresses and sales wastes the morning sorting them.
- Every submission goes straight into our newsletter tool and the first campaign bounced like crazy.
- People typo their own email on the demo request form and we have no way to reach them.
What you can do with Webflow and pingutil
Forward only verified leads to your CRM
Your webhook endpoint calls /v1/verify for the email field and pushes the lead to your CRM or list only when status is valid or risky. Invalid and disposable addresses stop at the endpoint.
Recover typos with did_you_mean
When the verification returns did_you_mean (jane@gmial.com suggests jane@gmail.com), post the suggestion to the sales channel with the original submission so someone can follow up on the right address.
Tag work-email leads with the company
For addresses that verify, a /v1/lookup call returns category and, for company domains, a company profile. Route company leads to sales and free webmail to the newsletter.
Clean junk out of the Webflow submissions list
Webflow's Data API has a Delete Form Submission endpoint (forms:write scope). Teams that keep submissions in Webflow can remove the ones that came back invalid.
Set it up
- 1
Create the webhook with the Data API (POST /v2/sites/:site_id/webhooks with triggerType "form_submission") using a site token or OAuth app, so requests carry x-webflow-signature. Dashboard-created webhooks are not signed.
- 2
Store the webhook secret (site token webhooks created on or after April 14, 2025 get their own) and your pingutil key as environment variables on your endpoint.
- 3
Verify the HMAC over "timestamp:body" and reject requests older than five minutes.
- 4
Return 200 right away and verify the email in the background; Webflow treats timeouts and non-200 responses as failures and retries.
- 5
Read the email from payload.data using the field name from your form, then forward or drop the lead based on status.
interface Env {
WEBFLOW_WEBHOOK_SECRET: string;
PINGUTIL_KEY: string;
}
async function hmacHex(secret: string, message: string): Promise<string> {
const key = await crypto.subtle.importKey('raw', new TextEncoder().encode(secret), { name: 'HMAC', hash: 'SHA-256' }, false, ['sign']);
const sig = await crypto.subtle.sign('HMAC', key, new TextEncoder().encode(message));
return [...new Uint8Array(sig)].map((b) => b.toString(16).padStart(2, '0')).join('');
}
async function verifyEmail(env: Env, email: string) {
try {
const res = await fetch('https://pingutil.com/v1/verify', {
method: 'POST',
headers: { authorization: 'Bearer ' + env.PINGUTIL_KEY, 'content-type': 'application/json' },
body: JSON.stringify({ email }),
signal: AbortSignal.timeout(25_000), // slow mail servers can take ~25 s
});
if (!res.ok) return null; // 429 / 5xx: fail open
return (await res.json()) as { status: string; reason: string; did_you_mean: string | null };
} catch {
return null; // timeout or network error: fail open
}
}
async function handleSubmission(env: Env, body: any) {
const email = String(body.payload?.data?.Email ?? '').trim(); // use your form's field name
if (!email) return;
const result = await verifyEmail(env, email);
if (result && result.status === 'invalid') {
console.log('dropped', body.payload?.name, result.reason, result.did_you_mean);
return;
}
// valid, risky, unknown or pingutil unreachable: forward to your CRM / list here
}
export default {
async fetch(req: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
const raw = await req.text();
const ts = req.headers.get('x-webflow-timestamp') ?? '';
const sig = req.headers.get('x-webflow-signature') ?? '';
const fresh = Math.abs(Date.now() - Number(ts)) < 5 * 60 * 1000;
if (!fresh || (await hmacHex(env.WEBFLOW_WEBHOOK_SECRET, ts + ':' + raw)) !== sig) {
return new Response('bad signature', { status: 401 });
}
const body = JSON.parse(raw);
if (body.triggerType === 'form_submission') ctx.waitUntil(handleSubmission(env, body));
return new Response('ok', { status: 200 });
},
};What to do with each result
| pingutil result | Action in Webflow |
|---|---|
| status: "invalid" (mailbox_not_found, no_mx, disposable_domain) | Do not forward the lead; optionally delete the Webflow submission. |
| did_you_mean is set | Send the suggestion to whoever owns follow-up along with the submission. |
| status: "risky" (accept_all, role_based) | Forward with a needs-review tag; catch-all domains cannot be confirmed. |
| status: "valid" | Forward to the CRM or email list as normal. |
| status: "unknown" or no response | Forward anyway and re-check later; never drop a lead because the check could not finish. |
Limits to plan for
- This is post-submission cleanup. Webflow stores the submission and shows the success message before your webhook runs, so the visitor is never asked to fix the address.
- Webflow retries a failed delivery up to three more times, 10 minutes apart, and deactivates webhooks that keep failing, so answer 200 quickly and do the verification in the background.
- Verification is budgeted per account (300 addresses a day, 3,000 a month). Busy forms may need /v1/lookup with skip_enrichment for screening and /v1/verify only for leads you forward. Those are Free plan limits; Enterprise has custom limits.
Webflow documentation
- developers.webflow.com/data/reference/webhooks/events/form-submission
- developers.webflow.com/data/docs/working-with-webhooks
- developers.webflow.com/data/reference/forms/form-submissions/delete-submission
Webflow is a trademark of its owner. This integration uses Webflow's documented extension points; it is not an official Webflow app.
Common questions
- Can I stop a Webflow form from accepting a bad email?
- Not with the native form and a webhook, because the webhook fires after Webflow has stored the submission. To block in the form itself you would need a custom form that posts to your own endpoint first.
- Why does my webhook have no x-webflow-signature header?
- Webhooks created in the Webflow dashboard are not signed. Create the webhook through the Data API with a site token or OAuth app to get signed requests.
Stop bad addresses in Webflow today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Webflow setup will receive.