// website builders and cms
Via APIFramer email verification with pingutil
A Framer form will happily send waitlist and contact submissions from temp-mail and typo addresses to your list or CRM. Framer can post each submission to a webhook you control, signed with a shared secret, so your endpoint can verify the address with pingutil before it goes anywhere. The visitor still sees Framer's success state, so this is cleanup after submit, not a block on the form.
Where it connects: Framer form "Send To" webhook destination, signed with Framer-Signature
What goes wrong without it
- Our Framer waitlist doubled overnight and half of it is throwaway inboxes.
- Launch-day email to the waitlist bounced hard and our sending domain took the hit.
- Investors ask how many real signups we have and I honestly cannot tell from the form export.
What you can do with Framer and pingutil
Keep the waitlist real
Verify every waitlist submission and add only valid and risky addresses to your email tool. Disposable addresses and dead mailboxes never reach the launch send.
Count genuine signups
Log status and reason for each submission so the number you report is the number of reachable people, not the number of form posts.
Spot company signups on a B2B waitlist
Call /v1/lookup for addresses that pass and record category and company.name, so you can prioritize invites for teams over personal accounts.
Set it up
- 1
In the Framer editor, select the form, open its Send To settings and add a webhook destination with your https:// endpoint URL.
- 2
Turn on signature verification by entering a secret of at least 32 characters; Framer shows it once, so store it as an environment variable next to your pingutil key.
- 3
Name the email input "email" in Framer, because the JSON body uses input names as keys.
- 4
On each request, recompute the HMAC-SHA256 of the raw body followed by the Framer-Webhook-Submission-Id header and compare it to Framer-Signature.
- 5
Return a 2xx status straight away; Framer retries non-2xx responses up to 5 times and does not follow redirects.
import { createHmac, timingSafeEqual } from 'node:crypto';
import { after } from 'next/server';
function validSignature(body: Buffer, submissionId: string, header: string): boolean {
const expected = 'sha256=' + createHmac('sha256', process.env.FRAMER_WEBHOOK_SECRET!)
.update(body)
.update(submissionId)
.digest('hex');
return header.length === expected.length && timingSafeEqual(Buffer.from(header), Buffer.from(expected));
}
async function verifyAndRoute(email: string) {
let result: { status: string; reason: string; did_you_mean: string | null } | null = null;
try {
const res = await fetch('https://pingutil.com/v1/verify', {
method: 'POST',
headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
body: JSON.stringify({ email }),
signal: AbortSignal.timeout(25_000),
});
if (res.ok) result = await res.json();
} catch {
// timeout or network error: treat as unknown and keep the lead
}
if (result?.status === 'invalid') {
console.log('skipped', email, result.reason, result.did_you_mean);
return;
}
// valid, risky, unknown: add to your list / CRM here
}
export async function POST(req: Request) {
const body = Buffer.from(await req.arrayBuffer());
const submissionId = req.headers.get('framer-webhook-submission-id') ?? '';
const signature = req.headers.get('framer-signature') ?? '';
if (!validSignature(body, submissionId, signature)) {
return new Response('invalid signature', { status: 401 });
}
const fields = JSON.parse(body.toString('utf8')) as Record<string, string>;
const email = (fields.email ?? '').trim();
if (email) after(() => verifyAndRoute(email)); // answer Framer first
return new Response(null, { status: 204 });
}What to do with each result
| pingutil result | Action in Framer |
|---|---|
| status: "invalid" | Do not add to the list; log reason (mailbox_not_found, disposable_domain, no_mx). |
| status: "risky" with reason accept_all | Add with a catch-all tag and watch engagement before the big send. |
| did_you_mean is set | Store the suggestion next to the submission for manual follow-up. |
| status: "valid" or "unknown" | Add to the list; re-check unknowns before a campaign. |
Limits to plan for
- Framer shows the form's success state before your webhook runs, so the visitor cannot be asked to correct a bad address.
- Framer documents retries (up to 5) but not a request timeout, so respond first and verify afterwards.
- Mailbox checks can take seconds and count toward the account's 300 verified addresses a day (3,000 a month); high-volume waitlists can screen with /v1/lookup (skip_enrichment) first. Those are Free plan limits; Enterprise has custom limits.
Framer documentation
Framer is a trademark of its owner. This integration uses Framer's documented extension points; it is not an official Framer app.
Common questions
- What does Framer sign?
- Framer computes an HMAC-SHA256 with your secret over the raw request body followed by the submission ID from the Framer-Webhook-Submission-Id header, and sends it as sha256=<hex> in Framer-Signature.
- Can I keep sending Framer submissions to my email tool directly?
- Yes, but then nothing filters them. Pointing the form at your webhook and forwarding from there is what lets pingutil drop the bad addresses first.
Stop bad addresses in Framer 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 Framer setup will receive.