How to Automate Catch-All Verification in HubSpot, Salesforce, and CRM Workflows?

If you landed here because a portion of your CRM contains unresolved catch-all email addresses and nobody wants to manually recheck them every week, you're in the right place.

You'll learn how to set up catch-all verification as an automated step inside HubSpot workflows and Salesforce Flow using Clearout Email Verifier. We have also included the right triggers to use, how to handle verification results, and how to automatically re-run checks.

Catch-all verification is the process of checking whether a mail server is configured to accept every message sent to its domain, regardless of whether the specific mailbox exists.

A catch-all domain will say "yes, I'll take that" to almost any address, including ones that were never created. That single behavior is why catch-all addresses cannot be judged as simply valid or invalid the way a normal inbox can.

Here's why manual checking falls apart quickly. A sales team adding 200 to 2,000 leads a week cannot pause and manually inspect each domain's mail server configuration. And even if someone did check today, that same domain could flip its catch-all setting next month with zero notice.

That is the entire case for automation. You need the check running every time a contact enters your CRM, and you need it running again on a schedule, not just once at import.

A verification tool connects to the domain's mail server and simulates the delivery attempt without actually sending an email. If the server accepts a message to a clearly fake, randomly generated address at that same domain, the tool knows the domain is a catch-all.

From there, it looks at supporting signals such as domain age, mailbox activity patterns, and historical deliverability data to assign a confidence score to the specific address you are checking.

This is why a good verification result for a catch-all address looks different from a normal valid or invalid flag. Instead of a flat yes or no, you get a status plus a score that tells you how likely that particular mailbox is to be real.

The challenge is that most email verification tools stop at identifying a catch-all domain.

They can tell you that the domain accepts all incoming email addresses, but they often cannot tell you whether the specific mailbox you're trying to reach actually exists.

That leaves sales and marketing teams with an uncomfortable choice:

This is where Clearout Deep Verify becomes useful.

Deep Verify is designed specifically for catch-all email addresses. Instead of leaving the address in an uncertain catch-all category, it performs additional analysis to determine whether the mailbox is more likely to be valid or invalid.

For teams running outbound campaigns, lead qualification workflows, or CRM automations, that additional layer of confidence can make routing decisions significantly easier.

You automate catch-all verification in HubSpot by building a workflow that triggers on contact creation or property change, then calls the Clearout API through a webhook or custom code action before the contact moves any further down your pipeline. The API response gets written back into a custom contact property, and the workflow branches from there.

Here is what that looks like in practice.

1. Create a contact-based workflow: Set the enrollment trigger to "Contact is created" or "Email address is known" for existing databases you are cleaning retroactively.

2. Add a filter for unverified contacts: Avoid re-running the check on records that have already passed by using a criterion such as "Verification Status is unknown".

3. Add a webhook or custom code action: An email address will be sent through Clearout Email Verifier. In addition to the typical validations, Clearout can detect disposable email addresses, role addresses, spam traps, and catch-all domains. It comes with a deep verification feature that runs multi-layer SMTP analysis. This detects the difference between a real mailbox and an "accept everything" reply.

4. Map the response to custom properties: Store the verification status, Deep Verify result, catch-all indicator, and safe-to-send flag as separate properties. These fields become the foundation for workflow branching, lead scoring, and routing decisions.

5. Branch the workflow based on those fields: Route valid and safe-to-send contacts forward, hold catch-all contacts for review, and suppress invalid ones from any sending list.

The webhook and custom code actions are available in HubSpot's paid workflow tiers, so check your plan before building this out. If your plan doesn't feature those actions, you can use a different middleware solution such as Zapier or Make, and connect HubSpot and Clearout API with the same trigger and branch logic.

The API call itself only needs the email address as input. What comes back matters more. You need the verification status, catch-all flag specifically, a numeric or categorical confidence score, and the safe-to-send indicator. All should be written into properties your reps and your other workflows can reference later.

Many CRM workflows treat catch-all emails as a single category.

Unfortunately, not each catch-all is at the same risk. Some come with high confidence scores and may be safe to outreach while a low-confidence catch-all will require further review.

Hence, verification should happen when a record is created, when an email address changes, and during periodic database hygiene reviews. Catch-all status can change over time as mailbox and domain configurations change.

Accuracy also improves when verification is triggered throughout the contact lifecycle instead of only at the point of capture.

Trigger points include:

Salesforce catch-all verification automation runs through Flow Builder rather than a native workflow tool. You build a record-triggered Flow on the Lead or Contact object, call out to the Clearout API through an External Service or a Named Credential plus HTTP callout, and update fields on the record with the result.

1. Configure authentication: Set up a named credential pointing to Clearout's API endpoint, so your org handles authentication securely instead of hardcoding a token in Apex.

2. Create trigger flow: Add a trigger to the flow, with the trigger set to on Create or on Update when the email field changes.

3. Call verification API: Add an Apex action or External Service call inside the Flow to send the email address and receive the verification response.

4. Store verification data: Analyse the output fields, such as Verification Status and Safe To Send.

5. Route as per results: Add decision elements after the callout so the Flow routes the record into the right queue, campaign, or list based on those field values.

One thing to flag here. Flow callouts to external services need to run asynchronously in most orgs, since synchronous callouts from a record-triggered Flow can hit governor limits if you are processing leads in bulk. Talk to whoever manages your org's Apex limits before rolling this out to a high-volume lead source.

Re-verify catch-all addresses based on how the lead entered your CRM and how long it has sat there, not on one fixed interval for your entire database.

One reason re-verification matters is that catch-all domains can change behavior over time.

An address that looked safe three months ago may carry a very different confidence level today. Running periodic verification through a service such as Clearout helps ensure routing decisions continue to reflect current mailbox conditions rather than historical assumptions.

Industry data consistently shows B2B email lists losing roughly 22.5 to 30% of valid addresses every year, which works out to a couple thousand dead contacts annually on a 10,000-record list. Catch-all addresses decay even less predictably, since a domain's mail server settings can change independent of whether the specific person still works there.

Here's a simple decision structure you can copy into your own workflow logic.

Before you trust this automation on your full pipeline, run it against a smaller, known sample first. Pull a batch of 200 to 500 contacts you already have some signal on, a handful you suspect are stale, and a few catch-all domains you have flagged before. Run them through the workflow exactly as you built it and compare the output against what you already know.

Here is what to check specifically:

Repeat this check whenever you alter your workflow logic or CRM's API version. If one of these gets updated and nobody notices, automation drifts quietly.

Most CRM workflows are good at moving data. Very few are good at evaluating email risk.

Clearout Email Verifier help you automate verification before contacts enter sales and marketing workflows by providing: