Skip to content

// forms and surveys

Via API

Fillout email verification with pingutil

Fillout forms often write straight to Airtable, Notion or a CRM, so a mistyped or throwaway email becomes a permanent record. Point a Fillout webhook in Advanced mode at a small function that checks a bearer token, verifies the email with pingutil and forwards only addresses that can receive mail. It runs after the submission is saved in Fillout, so it filters rather than blocks.

Where it connects: Fillout Webhook integration in Advanced mode (custom body fields and Authorization header)

What goes wrong without it

  • Our Fillout application form syncs to Airtable and the base is full of emails that bounce.
  • Someone submits ten times with different temp-mail addresses to get more referral credit.
  • The webhook failed once during a deploy and we had to retry submissions by hand.

What you can do with Fillout and pingutil

  • Verify applications before they reach your base

    Replace the direct Airtable sync with a webhook that forwards valid and risky submissions with the pingutil status as an extra field.

  • Spot referral and promo abuse

    Drop submissions where verdict.is_spam is true from a fast /v1/lookup, which catches disposable domains and randomized addresses used to farm rewards.

  • Route by company

    For applications from company domains, a full lookup returns the company name and size estimate so you can prioritize them.

Set it up

  1. 1

    Create a pingutil key and a random FILLOUT_TOKEN, and set both as secrets on your function.

  2. 2

    Deploy the Deno function below (Deno Deploy, Supabase Edge Functions or any Deno host).

  3. 3

    In Fillout, open Integrate, choose Webhook, switch to Advanced and set the URL to your function.

  4. 4

    Add body fields named email and submissionId mapped from the form, and a header Authorization with the value Bearer <FILLOUT_TOKEN>.

  5. 5

    Click Test, then publish the form again so real submissions use the new settings.

Deno function for a Fillout Advanced webhook
const PINGUTIL_KEY = Deno.env.get('PINGUTIL_KEY')!;
const FILLOUT_TOKEN = Deno.env.get('FILLOUT_TOKEN')!;
const CRM_WEBHOOK_URL = Deno.env.get('CRM_WEBHOOK_URL')!;

async function pingutil(path: string, body: object, ms: number) {
  try {
    const res = await fetch('https://pingutil.com' + path, {
      method: 'POST',
      headers: { authorization: 'Bearer ' + PINGUTIL_KEY, 'content-type': 'application/json' },
      body: JSON.stringify(body),
      signal: AbortSignal.timeout(ms),
    });
    return res.ok ? await res.json() : null;
  } catch {
    return null; // fail open
  }
}

Deno.serve(async (req) => {
  if (req.headers.get('authorization') !== 'Bearer ' + FILLOUT_TOKEN) {
    return new Response('unauthorized', { status: 401 });
  }

  // Advanced mode sends the flat body fields you defined in Fillout.
  const { email, submissionId } = (await req.json()) as { email?: string; submissionId?: string };
  if (!email) return new Response('ok');

  const fast = await pingutil('/v1/lookup', { input: email, skip_enrichment: true }, 3000);
  if (fast?.verdict?.is_spam) {
    console.log('fillout spam', submissionId, fast.verdict.reason);
    return new Response('ok');
  }

  const check = await pingutil('/v1/verify', { email }, 15000);
  if (check?.status !== 'invalid') {
    await fetch(CRM_WEBHOOK_URL, {
      method: 'POST',
      headers: { 'content-type': 'application/json' },
      body: JSON.stringify({
        email,
        fillout_submission_id: submissionId,
        email_status: check?.status ?? 'unchecked',
        did_you_mean: check?.did_you_mean ?? null,
        category: fast?.category ?? null,
      }),
    });
  }
  return new Response('ok');
});

What to do with each result

pingutil resultAction in Fillout
verdict.is_spam: trueDrop the submission from your base and rewards logic.
status: "valid"Forward to Airtable, Notion or the CRM.
status: "invalid"Do not forward; it stays visible in Fillout Results.
status: "risky" or "unknown"Forward with the status so reviewers can see it.
category: "company"Store it so company applications can be sorted first.

Limits to plan for

  • Fillout sends each webhook once and does not retry automatically. If your function or pingutil is down, the snippet fails open, and you can use Retry integration on the Results page for anything that failed.
  • In Advanced mode Fillout sends only the flat body fields you define, not the full submission, and it cannot send nested JSON.
  • The webhook runs after submission, so the respondent is never shown a verification error.

Fillout documentation

Fillout is a trademark of its owner. This integration uses Fillout's documented extension points; it is not an official Fillout app.

Common questions

Why use Advanced mode for the Fillout webhook?
It lets you add an Authorization header so your function can reject requests that did not come from your form, and it sends exactly the fields you need.
What happens if pingutil times out?
The submission is forwarded as unchecked. Because Fillout does not retry, failing open is safer than returning an error and losing the lead.

Stop bad addresses in Fillout 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 Fillout setup will receive.