Salesforce Phone & Email Validation Integration
Validate phone numbers and verify emails on Leads and Contacts in real time, with results mapped to custom fields you can report and automate on.
The 1Lookup Salesforce integration validates phone numbers and verifies emails on Leads and Contacts using Flow or Apex. A record-triggered Flow or trigger calls the 1Lookup REST API, then maps line type, carrier, and deliverability into custom fields, keeping Salesforce data clean and reportable without manual verification.
Why validate Salesforce records with 1Lookup
Bad contact data is expensive in Salesforce: it skews reports, wastes rep time, and inflates your database with unreachable Leads. 1Lookup adds a validation layer that checks each phone number and email against live carrier and deliverability data, so the records your team works are real and reachable.
1Lookup integrates through Salesforce's standard extensibility, a record-triggered Flow with an HTTP callout (via a Named Credential and External Service) or an Apex trigger for higher-volume or more custom logic. Results land in custom fields, so they are available to validation rules, list views, reports, and downstream automation.
What you can do
Real-time validation on Leads and Contacts
Validate phone and email when a record is created or updated, using a record-triggered Flow or Apex trigger.
Custom field mapping
Map 1Lookup's response (validity, line type, carrier, deliverability) into custom fields for reporting and segmentation.
Bulk validation workflows
Process existing records in batches with Apex or scheduled Flows, then act on the results across your database.
Named Credential security
Store the 1Lookup API key in a Named Credential so the key is never hard-coded in Flows or Apex.
How to connect 1Lookup to Salesforce
Create a 1Lookup account and API key
Sign up for 1Lookup and generate an API key. Use the free-tier lookups to test before you roll the integration out.
Set up a Named Credential
In Salesforce Setup, create a Named Credential pointing at the 1Lookup API base URL and storing your API key, so callouts authenticate securely.
Add custom fields for results
Create custom fields on Lead and Contact to hold validity, line type, carrier, and email deliverability.
Build a record-triggered Flow or Apex trigger
Add a record-triggered Flow with an HTTP callout (or an Apex trigger) that calls 1Lookup, then maps the response into your custom fields and applies any validation rules.
Use cases
Trustworthy pipeline reporting
Filter dashboards and forecasts to validated, reachable Leads so revenue reporting reflects real opportunities.
Fraud and junk-lead suppression
Flag disposable emails and VoIP numbers at intake so they never enter rep queues or paid follow-up.
Frequently asked questions
Do I need Apex, or can I use Flow?
Either works. A record-triggered Flow with an HTTP callout covers most real-time validation needs with no code. Apex is useful for high-volume bulk processing or more complex response handling.
How is the 1Lookup API key kept secure in Salesforce?
Store the key in a Named Credential. Flows and Apex reference the Named Credential rather than embedding the key, so it stays out of metadata and is managed centrally.
Can I validate Leads and Contacts I already have?
Yes. Use a scheduled Flow or Apex batch to run existing records through 1Lookup, then update the custom fields so historical data is cleaned alongside new records.