Verify emails in your Make scenarios

The YesWeCheck app adds address verification to your Make scenarios. A form, a lead or a spreadsheet row goes through YesWeCheck, SMTP included, and the rest of the scenario depends on the verdict: the valid contact joins your CRM, the invalid address is set aside before your first send.

Three steps, then your scenarios verify on their own

  1. Create a dedicated key

    In your dashboard, a key reserved for Make, with SMTP if you want it and a daily credit cap.

  2. Install the YesWeCheck app

    From your dashboard, add the app to your Make organisation, then paste the key into the connection: Make shows your account name.

  3. Plug it into your scenarios

    Place the verification module after your form or lead source, then route each contact by verdict.

Create my Make key

The app’s modules

Three modules, with the checks, SMTP, validation policy and lists set on your key. Every output is described in Make: you map it to the next module in one click.

Verify an address

Verify an email address

Verdict, a score from 0 to 100, disposable, free or business address, and the detail of each check, ready to map into the following modules.

Check the balance

Get credit balance

Credit balance and the key’s usage, to alert you before you run out. Free.

Call the API

Make an API call

Any other call to the YesWeCheck API, with the key already added: domain suggestions, first-name enrichment.

A typical scenario

The verdict does the routing. A Make router sends each contact down the right branch, and the score joins the contact record for your segments.

What happens to a contact depending on the verdict returned by YesWeCheck.
VerdictScenario branch
validContact created in the CRM, welcome email sent
invalidContact set aside, with an alert if you want one
riskyContact created with a “to check” tag
unknownContact created with a “to check” tag, no credit debited

Understand the score and the four statuses

Same credits, same rules

Make goes through the same engine as the API: an address gets the same verdict, whatever the route. One credit per address verified with SMTP, except when the result is undetermined; the balance module is free.

One key per use

Each scenario or each client can have its own key, stored with your API keys. You revoke it in one click.

A daily cap

A daily credit cap on the key: a badly configured scenario never touches the rest of your balance.

Your rules applied

The key’s checks, SMTP and validation policy apply to every verification coming from Make.

Discover the email validation API

Frequently asked questions

How do I verify an email address in a Make scenario?
Install the YesWeCheck app in your Make organisation, create a connection with a YesWeCheck API key, then add the Verify an email address module with the email field from the previous step. The module returns the verdict, the score and the detail of each check.
How much does a verification from Make cost?
Exactly as with the API: one credit per address verified with SMTP, except when the result is undetermined. The balance module is free.
Do I need to configure an HTTP module?
No. The YesWeCheck app handles authentication and describes every output: Result, Score, Checks and Metadata appear directly in the Make field picker.
Can a looping scenario drain my balance?
Not if you set a daily credit cap on the key used by Make. Once the cap is reached, the billed verifications of that key stop until the next day, without affecting your other integrations.
Can I keep my scenarios or clients separate?
Yes. Create one key per use: each has its own cap and statistics, and can be revoked on its own without stopping the other scenarios.

Get started

Create an account, generate a Make key and add verification to your first scenario.