// forms and surveys
Via APIJotform email verification with pingutil
Jotform posts every submission to your webhook whether the email works or not, so registrations, quote requests and order forms collect addresses that bounce. A receiver that answers Jotform fast and verifies the address in the background lets you forward only reachable contacts and flag the rest. Like most hosted builders, this is post-submit filtering; Jotform does not wait for your endpoint to approve the entry.
Where it connects: Jotform Webhooks integration (submission POST with the rawRequest field)
What goes wrong without it
- Half our event registrations from the Jotform page never get the confirmation email.
- We pay for a CRM seat per contact and Jotform keeps filling it with junk addresses.
- Our webhook times out because whatever we call after the submission is too slow.
What you can do with Jotform and pingutil
Confirm event and class registrations reach a real inbox
Verify the attendee address before your system sends tickets or joining links, and mark registrations with invalid emails so staff can call or text instead.
Screen quote and contact requests
Use /v1/lookup with skip_enrichment to separate company domains from free webmail and disposable addresses, then route business requests to sales and drop throwaways.
Clean an existing Jotform export
Download past submissions as CSV and run them through the pingutil dashboard CSV upload (50 rows per file) or /v1/verify/batch before importing them anywhere.
Set it up
- 1
Create a pingutil API key and add it to your Worker as the PINGUTIL_KEY secret, plus a random JOTFORM_TOKEN.
- 2
Deploy the Cloudflare Worker below. It accepts the multipart body Jotform sends and replies immediately.
- 3
In Jotform, open Settings, then Integrations, search for Webhooks and add your Worker URL with ?token=<JOTFORM_TOKEN> appended.
- 4
Submit a test entry and check the Worker logs for the rawRequest keys; Jotform names answers like q4_email, with the number depending on your form.
- 5
Adjust the email key match if your field is not named email, then set CRM_WEBHOOK_URL for clean submissions.
interface Env {
PINGUTIL_KEY: string;
JOTFORM_TOKEN: string;
CRM_WEBHOOK_URL: string;
}
async function verify(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(20000), // runs after the response, so it can wait longer
});
return res.ok ? await res.json<{ status: string; reason: string; did_you_mean: string | null }>() : null;
} catch {
return null;
}
}
async function handle(env: Env, submissionId: string, email: string) {
const result = await verify(env, email);
if (result?.status === 'invalid') {
console.log('jotform submission flagged', submissionId, result.reason);
return;
}
await fetch(env.CRM_WEBHOOK_URL, {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({
email,
jotform_submission_id: submissionId,
email_status: result?.status ?? 'unchecked',
did_you_mean: result?.did_you_mean ?? null,
}),
});
}
export default {
async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
const url = new URL(request.url);
if (request.method !== 'POST' || url.searchParams.get('token') !== env.JOTFORM_TOKEN) {
return new Response('not found', { status: 404 });
}
const form = await request.formData();
const answers = JSON.parse(String(form.get('rawRequest') ?? '{}')) as Record<string, unknown>;
// Jotform keys answers by field name, e.g. "q4_email". Check a test submission.
const emailKey = Object.keys(answers).find((k) => k.endsWith('_email'));
const email = emailKey ? String(answers[emailKey]).trim() : '';
if (email) ctx.waitUntil(handle(env, String(form.get('submissionID') ?? ''), email));
return new Response('ok'); // answer well inside Jotform's 5 second timeout
},
};What to do with each result
| pingutil result | Action in Jotform |
|---|---|
| status: "valid" | Forward to the CRM or send the confirmation email. |
| status: "invalid" | Hold the submission and flag it for staff; do not send tickets or links to it. |
| status: "risky" with reason accept_all | Forward, but tag it so a bounce does not surprise anyone. |
| did_you_mean is set | Include the suggestion in the staff alert so they can correct the record. |
| verdict.is_spam: true (from /v1/lookup) | Drop the submission from lead routing. |
Limits to plan for
- Jotform's documented default webhook timeout is 5 seconds (adjustable only on Enterprise), shorter than a slow mailbox check. Reply first and verify in the background, as the Worker does with waitUntil.
- Jotform sends multipart form data, not JSON. Answers are a JSON string in the rawRequest field, keyed by Jotform's own field names.
- Verification happens after Jotform has saved the entry. pingutil cannot stop the submission itself or edit it inside Jotform.
Jotform documentation
Jotform is a trademark of its owner. This integration uses Jotform's documented extension points; it is not an official Jotform app.
Common questions
- Why does my Jotform webhook show a timeout?
- Jotform waits about 5 seconds for your endpoint. Return a 200 straight away and run the email check afterwards, for example with waitUntil in a Cloudflare Worker.
- Can I read the Jotform webhook body as JSON?
- The request itself is form data. Parse it, then JSON-decode the rawRequest field, which holds the answers.
Stop bad addresses in Jotform 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 Jotform setup will receive.