emailfinder.dev + Make
Make's visual workflow builder lets you connect emailfinder.dev to any app in your stack — CRMs, spreadsheets, databases, outreach tools — using HTTP modules to call the API and map responses to your data.
What you can do with this integration
- ✓Enrich Airtable or Google Sheets prospect lists with verified emails
- ✓Trigger lookups from webhook payloads or database record changes
- ✓Build multi-step enrichment scenarios that combine person + LinkedIn lookups
- ✓Route enriched contacts to different outreach sequences based on role
How to set it up
Add an HTTP module
In your Make scenario, add an HTTP > Make a request module.
Configure the request
Set method to GET, URL to https://www.emailfinder.dev/api/find-email/person, and add query string parameters full_name and domain from your trigger module.
Add the Authorization header
Under Headers, add Authorization with value Bearer YOUR_API_KEY.
Parse and route the response
Map the valid_email field from the JSON response to downstream modules — update your CRM, write to a sheet, or trigger a campaign.
Code example
// Make HTTP module configuration
Method: GET
URL: https://www.emailfinder.dev/api/find-email/person
Query String:
full_name: {{1.full_name}}
domain: {{1.domain}}
Headers:
Authorization: Bearer YOUR_API_KEY
// Parse response body
{{body.valid_email}} → pass to next moduleMake integration FAQ
Does Make support all emailfinder.dev endpoints?
Yes. All four endpoints (person, company, linkedin, decision-maker) are available via HTTP module GET requests. Use the endpoint that matches your data — LinkedIn URL for LinkedIn exports, domain for company-wide enrichment.
How do I handle not_found responses in Make?
Add a Router after the HTTP module and filter one branch for when valid_email exists and another for when it's null. Route null results to a separate list for manual follow-up.
Can I run parallel lookups in Make?
Yes. Use Make's Iterator and Array Aggregator modules to process lists of contacts in parallel, subject to your Make plan's operations per minute limit.
Is Make cheaper than Zapier for this?
Make is generally more cost-effective for high-volume workflows because it charges per operation rather than per task, and operations are cheaper at scale.
Other integrations
Start integrating with Make
Free credits included. No credit card required. REST API with Bearer token auth.