Zapier: verify every new HubSpot contact and save the result on the contact

What you need

• A Zapier plan that includes Webhooks by Zapier
• HubSpot with permission to create contact properties
• A SimpleVerifier API key from simpleverifier.com/api-keys (starts with sv_live_)

Set it up

1. In HubSpot create two single-line text contact properties with internal names sv_status and sv_action.
2. In Zapier create a Zap. Trigger: HubSpot, event New Contact. Connect your HubSpot account and test it.
3. Action 1: Webhooks by Zapier, event Custom Request. Method POST, URL https://simpleverifier.com/api/v1/verify. Fill Data and Headers as shown above. Test the step. The output lists status, action, reason and reason_code.
4. Action 2: HubSpot, event Update Contact. Set Contact to the contact ID from the trigger. Map sv_status to status and sv_action to action from the webhook output.
5. Optional: add a Filter step before the update so only contacts with a non-empty email are checked.
6. Turn the Zap on and create a test contact to see the properties fill.

{"email": "<Email from the HubSpot trigger>"}

Authorization: Bearer YOUR_SIMPLEVERIFIER_API_KEY
Content-Type: application/json

Field mapping

Start with your own key

Every template calls the SimpleVerifier API with your key. Create one, then run the template on a handful of rows. To check a whole list without any setup, upload it as a CSV.

Common questions

Is there a one-click Zap link?

Not yet. A shared Zap link has to be published from a Zapier account. Until then the steps and field mapping above are the whole setup.

Does HubSpot have a native option?

Yes. SimpleVerifier connects to HubSpot directly and writes each result to an sv_status property without a Zap. Use this Zap if you want the check to run on each new contact inside your own Zapier flow.

Which SimpleVerifier plan do I need?

Pro is $39/month with 10,000 API and MCP calls included, then $1.50 per 1,000. Cancel anytime. Each key can make 120 calls a minute.

What do valid, risky and invalid mean here?

The result has a status and an action. Action send means the mail server confirmed the mailbox. send_with_care is a catch-all, role inbox or provider that hides mailbox status. retry_later means the check could not finish. do_not_send means the address will bounce or is a throwaway. Catch-all addresses are never marked valid.