Automate Email Verification
in Your Make.com Workflows
Add a real-time email check to any Make.com scenario by calling the Valid Email Checker API from the built-in HTTP module — no Make app to install. Verify a new signup, then use a Router to branch safe addresses into your CRM and route invalid ones out.
Verify-email scenario
Make.comTrigger (any app)
New signup / lead
Verify Email
Valid Email Checker
Add to CRM
Skip / tag
What You Need to Get Started
A Valid Email Checker API Key
Generate one on the Developer page. 150 free credits on signup.
A Make.com Account
Any plan that lets you add the built-in HTTP module to a scenario.
A Few Minutes
Drop in one HTTP module, paste your key, and you are verifying.
How to Build It in Make.com
No Make app required. You only need the built-in HTTP › Make a request module. Each step below mirrors the fields you fill in — copy the values straight across.
Have a Valid Email Checker account? Skip the manual setup.
Open Integrations → Automation & Workflows in your dashboard — the guided wizard generates an API key, shows these exact fields, and lets you run a live test, all in one place.
Add the HTTP module & set the endpoint
In your scenario, add a module and choose HTTP → Make a request. Set the method and URL:
Method
URL
Authenticate with a Bearer header
Set Authentication type to No authentication — you pass the key with a header instead of Make's built-in auth (don't pick Basic auth or OAuth 2.0). Then under Headers, click Add a header and enter:
Authentication type
Name
Value
Reusable connection: prefer to share the key across scenarios? Choose the API key auth type instead — parameter name authorization, key Bearer YOUR_API_KEY, placement Header.
Get your key: generate it on the API Access page in your dashboard.
Send the email as a JSON body
Set the body content type to JSON and enter the request body. In a real scenario, map the email from your trigger in place of the example address.
Body content type
Body input method
{
"email": "user@example.com"
}Parse the response & branch on the result
Set Parse response to Yes so Make reads the JSON. Then add a Router (or a Filter on a single route) and branch on the returned status — send deliverable addresses to your CRM and route the rest elsewhere.
Parse response
Filter condition — status equals
Inbound triggers: to start a scenario from an external event (a form submission, a new lead), front it with Make's Webhooks › Custom webhook module, then verify, then branch.
Single vs. Bulk — Which Endpoint?
Verify one address at a time as records flow through, or clean a whole list in one task. Both cost 1 credit per email.
Verify one at a time
DefaultPOST /api/verify-singleAs each record flows through your scenario — a form submission, a new CRM contact, a new row — verify that one email in real time before the next module runs.
The default for Make scenarios. It is what the step-by-step above uses.
Clean a whole list
BatchPOST /api/verify-bulkGET /api/get-results/{task_id}Periodically cleaning an existing list? Submit many emails as one task and poll for results — far more efficient than looping single HTTP calls.
Submitting as one task avoids the 60 requests/minute limit; the daily cap is 10,000 verifications.
What the API Returns
Every verification responds with a structured JSON object you can map into any later module.
statusVerdict: safe, invalid, risky, or unknown.
is_validBoolean — safe to send to.
is_disposableFlags throwaway / temporary domains.
is_role_accountFlags addresses like info@ or admin@.
is_catch_allDomain accepts mail for any address.
mx_foundWhether valid MX records exist.
risk_scoreNumeric risk indicator for the address.
credits_usedCredits charged for this request.
Why Verify Inside Make.com
Protect Your Sender Reputation
Stop invalid and disposable addresses before they ever enter your CRM or email tool.
Real-Time, Not Batch
Verify the moment a lead arrives — at signup, on a form submit, or as a webhook fires.
Branch on the Result
Use a Router or Filter to send clean leads one way and questionable ones another.
Credits & Billing
1 Credit = 1 Email
Same rate as bulk, dashboard, and API.
Unknown = Refunded
Credits returned for unverifiable emails.
150 Free Credits
Included on every new account.
60/min · 10k/day
Generous API rate limits.
Frequently Asked Questions
No. There is no Make app to install. You call Valid Email Checker through Make's built-in "HTTP › Make a request" module, which can send a POST request to any REST API. Any Make.com account that lets you add an HTTP module works.
1 credit per email — the same rate as bulk upload, the dashboard, and every other method. If we cannot reach a definitive answer and return "Unknown", that credit is automatically refunded to your account. Setting up the scenario and sending requests costs nothing on its own.
API keys are generated on the Developer page inside your Valid Email Checker dashboard. Create a key, copy it, and use it as the Bearer token in your Make HTTP module's Authorization header. You can revoke and regenerate keys at any time.
Yes. For large lists, use the bulk endpoint: POST to /api/verify-bulk with an array of emails, store the returned task_id, then poll GET /api/get-results/{task_id} for the results. The single-email endpoint is best for real-time, one-at-a-time flows like form submissions.
The API allows up to 60 requests per minute and 10,000 requests per day. For high-volume scenarios, add a small delay between HTTP modules or batch addresses through the bulk endpoint to stay within these limits.
Ready to Verify Emails in Make.com?
Sign up, grab your API key from the Developer page, and drop one HTTP module into your scenario. 150 free credits included — no credit card required.
Get Started Free150 free credits · No credit card · Built-in HTTP module