Salesforce phone and email validation

Why validate inside Salesforce

Salesforce orgs accumulate bad phone and email data from imports, web-to-lead and years of rep entry. Cleaning it once is a project; keeping it clean requires a check on create and update. Flow's HTTP Callout action can call LookupLab without Apex, and the response fields map straight to custom fields for reporting.

For orgs with a middleware layer (MuleSoft, Workato, Zapier), calling the API there is often simpler than building inside Salesforce.

Setup

1. Add a Named Credential for https://lookuplab.io with an Authorization header.
2. Create a Flow HTTP Callout action for GET /api/v1/phone/ with a number parameter.
3. Trigger the Flow on Lead create and update, and write data.line_type and data.valid to custom fields.
4. Build reports and validation rules on those fields.

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

• Block landlines from SMS cadences in Sales Engagement.
• Flag leads with disposable emails before assignment.
• Data quality dashboards by carrier and line type.

Related: HubSpotGoHighLevelPipedrive