Integrations / Make
Make phone and email validation
Drop a validation call into any Make scenario with the HTTP module.
Why validate inside Make
Make scenarios handle branching better than most automation tools, which makes them a good fit for validation: one path for valid mobiles, one for landlines, one for invalid numbers. The HTTP module calls LookupLab directly and the JSON parser exposes every field for routing.
Because Make bills per operation and LookupLab bills per successful lookup, invalid inputs cost you a Make operation but no LookupLab credit.
Setup
- Add an HTTP > Make a request module.
- Method GET, URL https://lookuplab.io/api/v1/phone/?number={{trigger.phone}}, header Authorization: Bearer YOUR_API_KEY, parse response Yes.
- Add a Router with filters on data.valid and data.line_type.
- Send each branch to its destination: CRM, SMS tool, review sheet.
What teams build with it
- Enrich every new Pipedrive deal with carrier and line type.
- Route VoIP signups to manual review.
- Verify emails before they enter a cold email sequence.
Get a key and connect Make
One API key, one credit pool, 1,000 free lookups to start. Phone, email, IP and DNS checks from a single endpoint, and you only pay for lookups that return an answer.
Start free Read the docsQuestions
Which module do I use?
HTTP > Make a request. No custom app is required.
Does it work with Make's free plan?
Yes, the HTTP module is available on every plan.