Connect Email Verification to the Tools You Already Use
Fifteen guides to running email verification inside the CRM, marketing platform, store, spreadsheet or automation tool where your contacts already live. Each one covers installation, field mapping, and what to do with every result status.
Underneath all fifteen guides below there are only two calls. The verification API checks a single address and answers inside the request that asked for it, which is what makes a real-time check possible inside a form or a workflow step. The bulk verifier takes a whole list and works through it as a background job. Everything a connector adds on top of those two is packaging: a trigger that decides when the call fires, and somewhere inside your platform to put the answer. Working out which of the two an integration leans on tells you most of what it can and cannot do, because a checkout app built around single-address calls has no opinion whatsoever about the customer records you imported last year, which is why the ecommerce and CRM guides here all document a bulk pass as well.
The part of setup that actually takes thought is where the answer lands. Every connector writes back the same four values — a status, a numeric risk score, an email type, and the time of the check — but each platform gives them a different container and a different name. Salesforce installs them as custom fields on the Lead, Contact and Account objects; Pipedrive puts EV Status, EV Risk Score, EV Email Type and EV Last Verified on the Person entity; Zoho CRM adds the equivalent fields to each module you enable; Klaviyo creates lowercase profile properties named ev_status, ev_score, ev_type and ev_verified_at. Read those names against what your platform already has before you approve an install, because a collision with a field your team is already using is considerably more annoying to unpick once records have been written over it.
On tag-based platforms the container is not a field at all, and that difference matters more than it looks. Mailchimp and ConvertKit apply tags instead — EV-Valid, EV-Invalid, EV-Risky and one more for unknown or disposable results — and Shopify tags customer profiles the same way after a bulk pass. A tag records membership and nothing else: it cannot hold a 0-100 score or a timestamp, so a rule like 'suppress everything above risk 70' or 'recheck anything not verified this year' has nothing to read from, and you refresh the four buckets by running the bulk job again. Where results land in fields, the score and the verified date are both filterable, which is what turns suppression into a standing segment rule rather than a task somebody has to remember. The form and checkout connectors sit at the far end of the same spectrum: WordPress and WooCommerce gate the submission and store nothing at all, so their configuration is a named strictness mode — Standard, Strict or Custom in WooCommerce, Block Invalid versus Block Invalid and Disposable in the Shopify app — rather than a field map.
When you are deciding which guide to open first, choose the system that owns the address permanently, not the one where it was first typed. The next thing to settle is which side of the connection holds the credential, because that decides who can actually perform the setup. The install-side connectors want your EmailValidationTool.org API key pasted into the platform, so whoever administers that platform does the work: the Salesforce AppExchange package, the Shopify app, the WordPress plugin, the Zoho Marketplace extension, the Airtable extension, the Google Sheets add-on, and the Zapier and Make modules. The dashboard-side ones run the opposite way, from the Integrations page in your account: HubSpot, Mailchimp and Pipedrive authorise over OAuth, while ActiveCampaign, Klaviyo and ConvertKit want that platform's own key pasted into ours. If your platform is not listed below, Zapier and Make reach most SaaS tools without code, and anything they miss can be handled by calling the API from your own code or exporting a CSV through bulk verification.
CRM and sales pipelines
The CRM is where an address lives longest, which is exactly why it decays there — imports, web forms and third-party sync all deposit records that nobody checks again. These guides cover writing verification status, risk score and last-verified date onto lead, contact and person records as custom fields, bulk-cleaning the database you inherited, and re-checking a contact before a sequence starts rather than after it bounces.
- Salesforce Integration Verify leads and contacts in Salesforce.
- HubSpot Integration Clean your HubSpot contacts automatically.
- Pipedrive Integration Verify sales pipeline contacts.
- Zoho CRM Integration Clean your Zoho contact database.
Email marketing platforms
Your marketing platform bills you by contact and judges you by bounce rate, so this is where the pre-send clean pays for itself twice. Each guide focuses on storing the verification result as a profile property or tag that a segment can exclude, so suppression becomes a standing rule instead of a manual step someone forgets. Klaviyo and ActiveCampaign lean toward ecommerce flows and automation branching; Mailchimp and ConvertKit lean toward newsletter and creator audiences.
- Mailchimp Integration Verify Mailchimp subscriber emails.
- ActiveCampaign Integration Clean your automation lists.
- Klaviyo Integration Clean ecommerce email lists.
- ConvertKit Integration Protect your creator subscriber lists.
Ecommerce checkout
Checkout is the highest-stakes place to verify, because a wrong answer either lets a fake order through or blocks someone who was about to pay you. Both guides cover inline verification at checkout and at account registration, choosing a strictness mode that catches invalid and disposable addresses without punishing catch-all corporate domains, and bulk-verifying the customer records you already have before the next campaign goes out.
- Shopify Integration Verify customer emails at checkout.
- WooCommerce Integration Validate customer emails at checkout.
Automation and no-code connectors
Reach for these when the system holding your addresses has no integration of its own, or when the check needs to sit between two tools rather than inside either one. Both put a verification step into a workflow you build visually, with branching so valid, invalid and risky results take different paths. Make adds iterators, routers and error handling for batch and multi-branch scenarios; Zapier is the faster route for a straightforward trigger-then-verify-then-route chain.
- Zapier Integration Automate email verification across 6,000+ apps.
- Make Integration Build visual verification workflows.
Spreadsheets, bases and your website
Lists that arrive as a file, a base or a form submission are the cheapest data to fix, because nothing downstream has copied them yet. Google Sheets and Airtable let you verify a column in place and keep the results next to the data, which suits event lists, agency handovers and anything assembled from several sources. The WordPress plugin works the other way round, rejecting bad addresses at submission time across the usual form plugins so they never enter your list at all.
- Google Sheets Integration Verify emails directly in spreadsheets.
- Airtable Integration Validate emails in your bases.
- WordPress Integration Real-time form email verification.
Every integration on this page authenticates with the same API key and draws on the same pool of verification credits, and they all map the same response fields into your platform, so the quickest way to get any of them working is to read the endpoint reference and generate a key first.
View the API docsIntegrations FAQ
The payload is small and consistent across all fifteen: a verification status, a numeric risk score, an email type such as personal, role-based, disposable or catch-all, and the date the check was made. What changes is the container. Salesforce, Pipedrive, Zoho CRM and ActiveCampaign create custom fields on the record along the lines of EV Status, EV Risk Score, EV Email Type and a verified-date field; HubSpot uses custom contact properties; Klaviyo creates profile properties named ev_status, ev_score, ev_type and ev_verified_at; Mailchimp, ConvertKit and Shopify apply tags rather than fields; Airtable and Google Sheets write into columns beside your data.
On the tag-based platforms the names are yours to change, and the defaults follow an EV-Valid, EV-Invalid, EV-Risky pattern you can rewrite to match your own conventions. On the field-based ones, review the field list the package installs before you approve it, so nothing collides with a property your team already relies on.
Usually, yes. Check first whether it has a Zapier or Make connector, because a verification step inside either one reaches most SaaS tools without anyone writing code. If it does not, the verification API accepts a single address over HTTPS and returns JSON, which any platform with webhooks, a scripting layer or a custom-code step can call directly. And if the platform can only export a spreadsheet, run the export through bulk verification and re-import the cleaned file — that path works everywhere, regardless of what the vendor supports.
Store them, do not delete them. A catch-all verdict is an absence of evidence rather than a negative result, and a great many legitimate corporate domains produce it, so deleting on that basis throws away contacts you may already have a working relationship with.
The right move inside an integration is to let the stored value decide per campaign rather than per contact: exclude catch-all and risky addresses from cold outreach and re-engagement sends, keep them for transactional mail and for people who have already replied. On field-based platforms that is a segment filter on status and score; on tag-based ones it is an exclusion on the EV-Risky tag, which is coarser but does the same job.