Verify emails in Make
Use Make's HTTP module to check each address in a scenario, then add a router so only valid addresses continue.
Setup
- Create an API key at simpleverifier.com/api-keys. It starts with sv_live_. API access comes with selected paid plans; a key on a plan without it gets a 402 that says so.
- In your scenario, add HTTP then Make a request after the module that outputs the email.
- Set URL to https://simpleverifier.com/api/v1/verify, Method to GET, and add a query string item named email mapped to your email field.
- Under Headers add Authorization with the value Bearer followed by your key. Set Parse response to Yes.
- Run the module once. The output bundle contains status, reason, send_advice and reason_detail.
- Add a Router with one route filtered on status equal to valid. Send the other statuses to a log or tag route.
Using the result
Route on the status field: valid means the mail server confirmed the mailbox, risky means delivery could not be confirmed (catch-all domain, role address, provider that hides mailbox status), invalid means it will bounce or is a throwaway address. Keep risky out of cold sequences unless you accept the bounce risk.
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Common questions
- Which plans include API access for Make?
- API access comes with selected paid plans, listed on the pricing page. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- Is there a SimpleVerifier app in Make?
- Not yet. The HTTP module covers it today.
- What if the call takes a long time?
- A slow mail server can take up to about 30 seconds. Raise the HTTP module timeout to 40 seconds.