Close Forms Accept Any Formatted Email: How to Check Form Leads Before They Hit a Sequence

SimpleVerifier Team·3 November 2026·3 min read

Key takeaways

Close's Forms article says a form accepts any properly formatted email address, with no third-party verification, no business-email restriction and no typo correction. Forms have basic spam prevention.
A form submission creates or updates CRM records and can trigger a Workflow at once, so a mistyped or fake address can be in a sequence within minutes.
Zapier's Close app has a New Form Submission trigger and Update Lead and Update Contact actions. Put an email check between them.
Write the result to a custom field, and only subscribe valid contacts to the sequence. Send risky ones (catch-all, role) to a rep to review rather than dropping them.
A check catches dead, mistyped and disposable addresses. It doesn't catch a real address typed by someone who isn't the person, so keep basic spam prevention on.

Close's native forms accept any properly formatted email address, with no verification and no typo correction, and a submission can start a Workflow right away. So a mistyped gmial.com or a throwaway address can be in a sequence, and bouncing from a rep's mailbox, within minutes. Put a check between the form and the sequence: Zapier's Close app triggers on New Form Submission, an email verification API checks the address, and only valid contacts are subscribed to the Workflow.

Sources, read 2 November 2026: Close's Forms article and its email deliverability guide, and the list of triggers and actions on Zapier's Close app.

What Close's forms do and don't do

Validation: "The form will accept any properly formatted email address without additional verification." No business-email restriction, no third-party verification, no typo correction.
Spam: "Forms include basic spam prevention." No CAPTCHA is mentioned.
On submit: creates or updates CRM records from your field mappings, and a Workflow can start from the Form Submission event.
Custom fields: form fields can map to Close custom fields, which is where a verification result can live.

Close's deliverability guide also says to stop sending to addresses that bounce permanently. A check before the sequence means fewer of those to begin with.

Put a check between the form and the sequence

You'll need a SimpleVerifier API key (API access comes with Pro and up) and a Zapier account.

Add a custom field in Close for the result, for example "Email check" with values valid, risky and invalid.
Don't start the sequence from the form directly. If a Workflow is set to trigger on Form Submission, switch it off for this form; Zapier will subscribe contacts instead.
Trigger: in Zapier, Close, New Form Submission.
Check the email: add Webhooks by Zapier, Custom Request. POST to https://simpleverifier.com/api/v1/verify with the email from the submission, and your key as a Bearer Authorization header. The full setup is on the Zapier integration page.
Write the result: Close, Update Contact (or Update Lead), setting the custom field to the returned status.
Branch with Paths: valid goes to Close, Subscribe Contact to Workflow. Risky creates a task for a rep. Invalid gets no sequence.

Test with your own address, a mistyped one and a made-up one before turning it on.

What to do with each result

Result	What it usually means	What to do
Valid	The mailbox exists	Start the sequence
Risky	Catch-all domain, role inbox, or the server wouldn't say	Rep reviews, or one personal email first
Invalid	No such mailbox, dead domain, or bad syntax	No sequence; ask for a corrected address if you can reach them another way

Don't drop risky results automatically. Many catch-all addresses are real company inboxes. Our catch-all leads in sequences post covers how to handle them.

What a check doesn't stop

A verifier tells you whether a mailbox exists. It can't tell you whether the person who typed it owns it. A real address entered by a bot or a competitor will pass. Keep Close's spam prevention on, and consider a confirmation email for high-value forms; see double opt-in vs verification and honeypot fields.

Leads already in Close

For leads that came in before you added the check, export a Smart View and verify the file. The Close export tool prepares it, and verify emails in Close CRM covers writing results back.

Where SimpleVerifier fits

SimpleVerifier has no Close connector; it works through the API (Pro and up) or a CSV. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off, and includes 10,000 API calls a month; on monthly billing, calls past that are billed per 1,000. The first 100 checks are free with a Google sign-in on the verify page. See pricing and the API docs.

Common questions

Does Close validate emails on its forms?

Only the format. Close's Forms article says the form accepts any properly formatted email address without additional verification, with no business-email restriction and no typo correction.

How do I verify Close form submissions?

Use Zapier's Close app: trigger on New Form Submission, call an email verification API with Webhooks by Zapier, write the result to a custom field with Update Lead or Update Contact, and only subscribe valid contacts to your Workflow.

Should I reject catch-all emails from a Close form?

No. A catch-all domain accepts every address, so a check can't confirm the mailbox, but many are real company addresses. Tag them risky and let a rep review or send a single personal email first.

Can I block disposable emails on a Close form?

Close's native form doesn't offer that option. An API check after submission can flag disposable addresses so they never enter a sequence.

Check your list before you send

Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.