Make template
Make: verify new Google Sheets rows and write the result back
Import one blueprint into Make. Each new row in your sheet is checked with the SimpleVerifier API and its status, action and reason are written back to the same row.
About 10 minutes to set upAnyone who collects leads or sign-ups in a sheet and wants every row marked before it is used.
How it runs
- 1
Watch rows
Google Sheets Watch New Rows module picks up each new row.
- 2
Verify
HTTP module posts the email to the SimpleVerifier verify endpoint.
- 3
Mark the row
Google Sheets Update a Row writes status, action and reason into columns B, C and D.
What you need
- A Make account
- A Google Sheet with the email in column A
- A SimpleVerifier API key from simpleverifier.com/api-keys (starts with sv_live_)
Set it up
- In Make create a scenario, open the three dots menu at the bottom and choose Import Blueprint. Pick the downloaded file.
- Open the first module, connect your Google account and choose your spreadsheet and sheet. Do the same in the last module.
- In the HTTP module replace YOUR_SIMPLEVERIFIER_API_KEY in the Authorization header with your key. To keep it out of the scenario, store it in a Make data store or custom variable and map it instead.
- Run once on a sheet with a few rows. Check that columns B, C and D fill in. Then switch the scenario on.
What each module sends
| HTTP URL and method | POST https://simpleverifier.com/api/v1/verify |
|---|---|
| HTTP body (JSON) | {"email": "<column A of the new row>"} |
| Column B | status from the response |
| Column C | action from the response |
| Column D | reason from the response |
Where your judgment still matters
The blueprint assumes the email is in column A and writes to B, C and D. If your layout differs, change the mapping in the first and last modules. Make updates its modules over time, so if Make marks one as outdated, re-add it and copy the settings from this page. Treat risky rows as a decision for you, not as a pass.
Start with your own key
Every template calls the SimpleVerifier API with your key. Create one, then run the template on a handful of rows. To check a whole list without any setup, upload it as a CSV.
Common questions
- Does this import without edits?
- The file follows Make's blueprint format. You still connect your own Google account and pick your sheet, because a blueprint never carries connections. If Make flags a module version, re-add the module and copy the settings listed above.
- Where should the API key live?
- The blueprint holds a placeholder. Paste your key in the HTTP module, or map it from a Make data store so the key is not in the scenario export.
- Which SimpleVerifier plan do I need?
- Pro is $39/month with 10,000 API and MCP calls included, then $1.50 per 1,000. Cancel anytime. Each key can make 120 calls a minute.
- What do valid, risky and invalid mean here?
- The result has a status and an action. Action send means the mail server confirmed the mailbox. send_with_care is a catch-all, role inbox or provider that hides mailbox status. retry_later means the check could not finish. do_not_send means the address will bounce or is a throwaway. Catch-all addresses are never marked valid.
Related: Verify emails in Make · Google Sheets add-on · API docs
All workflow templates · By SimpleVerifier Team