Skip to content

// website builders and cms

Via automation

Squarespace email verification with pingutil

Squarespace has no server-side hook on form submissions or member signups, so junk addresses go wherever the form sends them. A form block can use Zapier as a storage option, which lets a Zap verify the address with pingutil and filter it before it reaches your mailing list, CRM or sheet. This is post-submit cleanup; the visitor's submission is accepted either way.

Where it connects: Form block storage connected to Zapier, Squarespace Forms "New Form Submission" trigger

What goes wrong without it

  • The newsletter block on our Squarespace site collects so many fake emails that our open rate looks broken.
  • Contact form leads go into the CRM with typos in the email and we cannot reply to half of them.
  • Squarespace will not let me add any validation beyond "is this an email", and that is not enough.

What you can do with Squarespace and pingutil

  • Verify contact-form leads before the CRM

    Zapier runs a Code step that calls /v1/verify, then a Filter step lets only valid and risky results continue to the CRM action.

  • Keep the newsletter list clean

    Connect the newsletter block to Zapier instead of a mailing list directly, and add subscribers in your email tool only after the check passes.

  • Log rejects for review

    Send invalid results to a Google Sheet with the reason and did_you_mean, so someone can rescue the occasional mistyped real lead.

Set it up

  1. 1

    In Zapier, create a Zap with the Squarespace Forms app and the New Form Submission trigger, and pick your form.

  2. 2

    In Squarespace, edit the form block, open Storage, and connect Zapier; it shows Awaiting Connection until the Zap side is done.

  3. 3

    Add a Code by Zapier step (JavaScript) with input fields email (from the submission) and key (your pingutil key), using the code below.

  4. 4

    Add a Filter step that continues only when status is not invalid.

  5. 5

    Add your destination action (CRM, email tool or sheet) after the filter, then submit a test entry from the live site.

Code by Zapier (JavaScript) step
// Input Data: email = the form's email field, key = your pingutil API key
const controller = new AbortController();
const timer = setTimeout(() => controller.abort(), 8000);

let result = { status: 'unknown', reason: 'check_skipped', did_you_mean: null, score: null };
try {
  const res = await fetch('https://pingutil.com/v1/verify', {
    method: 'POST',
    headers: { Authorization: 'Bearer ' + inputData.key, 'Content-Type': 'application/json' },
    body: JSON.stringify({ email: inputData.email }),
    signal: controller.signal,
  });
  if (res.ok) result = await res.json();
} catch (e) {
  // timeout or network error: keep the lead as unknown
} finally {
  clearTimeout(timer);
}

output = {
  status: result.status,
  reason: result.reason,
  score: result.score,
  did_you_mean: result.did_you_mean || '',
};

What to do with each result

pingutil resultAction in Squarespace
status: "invalid"Filter stops the Zap; optionally log to a sheet with reason.
did_you_mean is setRoute to a review sheet with the suggested address.
status: "risky"Continue with a tag such as catch-all or role address.
status: "valid" or "unknown"Continue to the CRM or email tool.

Limits to plan for

  • Zapier can only be connected to Form Blocks, Newsletter Blocks and Cover Page forms, and Squarespace says a Business or Core plan or higher is required. Promotional pop-ups and custom HTML forms are not supported.
  • Squarespace does not store submissions sent to Zapier, and member-area or customer-account signups have no equivalent trigger, so this covers forms only.
  • Code by Zapier steps have plan-dependent run-time limits, so the snippet gives up after 8 seconds and marks the lead unknown. Slow mail servers can hit that.

Squarespace documentation

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

Common questions

Can I validate the email on the Squarespace form itself?
Not beyond the built-in format check. Squarespace forms do not run custom server code, so verification happens in the Zap after the visitor submits.
Should I keep the pingutil key in the Code step?
Pass it as an input field rather than typing it into the code, and limit who can edit the Zap. Anyone with edit access to the Zap can read it.

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