How to Verify New HubSpot Contacts With Zapier

To verify new HubSpot contacts with Zapier, build a three-step Zap: HubSpot New Contact, then Webhooks by Zapier Custom Request to the SimpleVerifier verify endpoint, then HubSpot Update Contact to save status and action on the contact. Your lists and workflows can then use those properties. This takes about 15 minutes.

The matching template page is zapier-hubspot-verify-contact. There is no importable file for this one, so the guide below is the full setup.

What you need

• A Zapier plan that includes Webhooks by Zapier.
• HubSpot with permission to create contact properties.
• A SimpleVerifier API key from the API keys page. It starts with sv_live_.

Step 1: create two HubSpot properties

In HubSpot, create two single-line text contact properties. Give them the internal names sv_status and sv_action. The Zap will fill them in. If you already have old contacts, a separate guide covers checking existing HubSpot contacts.

Step 2: set the trigger

Create a Zap. For the trigger choose HubSpot and the event New Contact. Connect your HubSpot account and test the trigger so Zapier has a sample contact with an email.

Step 3: add the verify call

Add an action: Webhooks by Zapier, event Custom Request. Fill it in like this:

• Method: POST
• URL: https://simpleverifier.com/api/v1/verify
• Data: {"email": "<Email from the HubSpot trigger>"}
• Headers: Authorization: Bearer YOUR_SIMPLEVERIFIER_API_KEY and Content-Type: application/json

Pick the Email field from the trigger step instead of typing the placeholder. Put your real key in the header. Test the step. The output lists status, action, reason and reason_code. The API docs explain each one.

Step 4: save the result on the contact

Add a second action: HubSpot, event Update Contact. Set Contact to the contact ID from the trigger. Then map:

HubSpot property	Value from the webhook output
sv_status	status
sv_action	action

Step 5: optional filter

Add a Filter step before the verify call so only contacts with a non-empty email are checked. This avoids a wasted call on contacts created from a phone number or a form without email.

Step 6: turn it on and test

Turn the Zap on. Create a test contact in HubSpot with an address you know is real, then one you made up. Watch the two properties fill in.

What to do with the values

The action value tells you what to do:

• send: the mail server confirmed the mailbox.
• send_with_care: a catch-all domain, a role inbox or a provider that hides mailbox status.
• retry_later: the check could not finish.
• do_not_send: the address will bounce or is a throwaway.

A good first rule is to enroll only contacts where sv_action is send. Decide separately what your team does with the others. Catch-all domains are a real share of any business list. In the catch-all study, 39.1% of 4,943 sampled business domains accepted a made-up address.

Things to watch

• A Zap runs once per new contact. If a rep later fixes a typo in the email, the Zap does not run again unless you add a trigger for updates.
• Each key can make 120 calls a minute. A normal flow of new contacts is far below that. See pricing for what your plan includes for API calls.
• A slow mail server can take about 30 seconds to answer. Zapier waits for it.

If a run fails

Open the Custom Request step in Zap history and read the response. The common answers are:

• 401: the key was not accepted. Check it on the API keys page and make sure the header reads Bearer, a space, then the key.
• 402: your plan does not include API access or is not active.
• 429: you hit the rate limit. The answer carries a Retry-After header, and Zapier can replay the run.
• 400: the body was not valid JSON or the email field was empty. Add the Filter step from earlier to prevent it.

Fix the cause, then replay the run from Zap history so the contact gets its properties.

How to use the properties in HubSpot

Once the two properties fill in, you can use them like any other contact property:

• Build an active list of contacts where sv_action is send, and use that list for sequences and marketing email.
• Build a second list where sv_action is do_not_send and exclude it from every send. Review it monthly in case a mailbox has changed.
• Build a list for retry_later and send_with_care and have someone decide what to do with it. A catch-all domain might be fine for a one-to-one rep email and wrong for a bulk send.

Keep the rule written down where your team can see it. A property nobody reads does nothing.

Where your judgment still matters

A property is a label, not a decision. Decide what a HubSpot list or workflow does with send_with_care contacts. Keep your sequences to sv_action = send until you are happy with the risky group.

For the sequence side, read verify before enrolling in HubSpot sequences. For a general Zapier walkthrough, see verify leads automatically with Zapier. If you also have HubSpot bounces to clean, see HubSpot bounce rate too high.

Frequently asked questions

Is there a one-click Zap link? Not yet. Use the steps above.

Is there a native HubSpot option? Yes. SimpleVerifier connects to HubSpot directly. The Zap is for people who want the check inside their own Zapier flow.

Which plan do I need? A Zapier plan with Webhooks by Zapier, and a SimpleVerifier plan with API access.