Make integration
Verify inside any Make scenario.
Make's HTTP module speaks to the Verifyre API directly. Add it after your trigger, parse the response, and route on the verdict.
What it does
Verifyre and Make, together.
One HTTP module
The built-in HTTP > Make a request module calls Verifyre with the email from the previous module and parses the JSON into mappable fields.
Route on the result
Use a Router with filters on status or score: deliverable leads go to the CRM, undeliverable ones to a Google Sheet or a Slack alert.
Bulk too
An Iterator over an array of addresses, or one POST to /api/v1/bulk for lists up to 50,000 with a webhook back into Make when it completes.
Setup guide
Set up Make in 3 steps.
You will need a Verifyre account (free, 100 credits) and an API key from Settings, then API keys.
Add an HTTP module
After your trigger, add HTTP > Make a request and configure it exactly as below. Turn on Parse response so the fields become mappable.
textModule: HTTP > Make a request URL: https://verifyre.co/api/v1/verify Method: GET Headers: Name: Authorization Value: Bearer vfy_live_YOUR_API_KEY Query: Name: email Value: {{1.email}} Body type: empty Parse response: YesRun once and inspect
Run the scenario once with a real address. Open the HTTP module's output bubble: data.status, data.reason, data.reason_text, data.score and data.did_you_mean are now available to every module after it.
Add a filter or router
Put a filter on the next route so only deliverable addresses continue, and optionally a second route for undeliverable ones to log and review.
textFilter (on the route after the HTTP module) Condition: {{2.data.status}} Equal to deliverable Mapped fields available after parsing: {{2.data.status}} {{2.data.reason}} {{2.data.reason_text}} {{2.data.score}} {{2.data.did_you_mean}} {{2.data.normalized}}
Write-back
What gets written back to your stack.
Verification only reads. Writing results back is a separate step you trigger after reviewing the counts, and nothing is ever deleted without your say-so.
- Nothing is written to Verifyre; map the verdict into whatever the scenario updates next: a CRM field, a tag, a sheet row.
- Use data.normalized as the de-duplication key when you upsert contacts: Gmail dots and plus tags are already removed.
Make FAQ
Make questions
Does Make count the HTTP call as an operation?
How do I handle a 402 or 429 response?
More like this