Zapier phone and email validation

Why validate inside Zapier

Zapier is where most teams already move leads between forms, CRMs and spreadsheets. Adding a validation step means every lead that flows through gets checked before it hits the CRM, and bad numbers or throwaway emails get routed to a separate path instead of poisoning the list.

LookupLab has no app in the Zapier directory yet; you use the built-in Webhooks by Zapier action, which is available on every paid Zapier plan. The setup below takes about five minutes.

Setup

1. Add a Webhooks by Zapier action after your trigger and choose GET.
2. Set the URL to https://lookuplab.io/api/v1/phone/ (or /email/ or /ip/) and add a query param: number, email or ip mapped from the trigger.
3. Add a header Authorization with the value Bearer YOUR_API_KEY.
4. Use a Filter or Paths step on data.valid and data.line_type to route bad records away from the CRM.

Phone validation is not consent, ownership verification or guaranteed delivery. Email syntax and MX checks establish domain-level signals, not proof that a particular mailbox exists.

What teams build with it

• Check every Facebook Lead Ads number before it reaches the dialer.
• Reject disposable emails on Typeform submissions.
• Tag HubSpot contacts with carrier and line type.

Related: Maken8nSlack