
Salesforce integration
Verify new Salesforce leads before anyone works them
Each new lead's email is checked as the record is created, so reps and sequences start from addresses that can actually receive mail.
- CRM and sales
- No code
- Set up in minutes
- Premium on Zapier
The Zap
- 1
Trigger · SalesforceNew Lead Verdict
SafeRiskyInvalidUnknown
- Starts from
- New Lead
- BounceIntel step
- Verify Email Address
- You get back
- Verdict, score, reason and mailbox signals
- Zapier plan
- A paid plan, because Salesforce is a Premium app
01Zaps
Start from a template
Each template opens in Zapier's editor with Salesforce and BounceIntel already set up. Connect both accounts, check the field mapping, and turn it on.
Verify new Salesforce leads with BounceIntel
New Lead
Verify Email AddressOr build your own
New Lead
Verify Email AddressAny Salesforce trigger that carries an email address can start a check. Pick it in Zapier, then add Verify Email Address and map the email.
02Why it matters
Why verify Salesforce emails
Salesforce leads come from web-to-lead forms, list purchases, event scans and reps pasting in contacts from LinkedIn. A good share of those addresses are guessed, mistyped or belong to people who left the company, and Salesforce has no way of telling which.
The cost is paid by the sales team first: sequences that bounce, reps chasing leads that were never reachable, and a sending domain that starts to look careless to Microsoft and Google. Verifying when the lead is created keeps that noise out of the pipeline and out of your reports.
03Ideas
What to do with the verdict
The check on its own changes nothing. These are the steps that make it pay off inside Salesforce.
Add verdict fields to the Lead object
Create a picklist for the verdict and a number field for the score, then map them in an update record step. Lead views and assignment rules can use them straight away.
Hold invalid leads back from assignment
Filter the Zap on the verdict and update invalid leads to a status your assignment rules skip, so no rep picks up a lead that cannot be emailed.
Use the typo suggestion
When Did you mean has a value, write it to a field or a task. Many web-to-lead errors are a single wrong letter in the domain, and the suggestion saves the lead instead of discarding it.
04Setup
Set it up in four steps
- 1
Get your API key
Create a key on the API keys page of your BounceIntel dashboard. Keys come with any paid plan and start with bi_live_.
- 2
Start the Zap in Salesforce
In Zapier, choose Salesforce as the trigger app and pick New Lead, or open a template above, which does this for you.
- 3
Add Verify Email Address
Add BounceIntel as the action, connect it with your key, and map the email field from Salesforce into the Email field.
- 4
Act on the verdict
Add a Filter on Safe to send, Paths on the verdict, or an update step that writes the verdict and score back to Salesforce.
05Fields
What each check returns
The fields to map first. Every check also returns reason codes, a confidence level, the mail provider and the individual mailbox signals.
- Verdict
is_reachable - Safe, risky, invalid or unknown. The field to filter or branch on.
- Score
score - 0 to 100. Worth writing back so lists and reports can sort by it.
- Safe to send
safe_to_send - One true or false value, ready for a Filter step.
- Reason
sub_reason - Why the verdict was chosen, in plain words.
- Disposable address
is_disposable - A throwaway inbox from a temporary mail service.
- Role account
is_role_account - A shared inbox such as info@ or sales@ rather than a person.
- Catch-all domain
smtp_is_catch_all - The server accepts every address, so the mailbox cannot be confirmed.
- Did you mean
domain_suggestion - A corrected domain when the address looks like a typo, such as gmial.com.
06Questions
Salesforce and BounceIntel: common questions
Do I need a paid Zapier plan for Salesforce?
Yes. Zapier lists Salesforce as a Premium app, so it is only available on paid Zapier plans. The BounceIntel side works on any plan.
Can the check run on contacts as well as leads?
Yes. The template starts from new leads, but you can swap the trigger for new contacts or a new record of any object that holds an email field, and map that field into the BounceIntel step.
How many BounceIntel credits does this use?
One credit for each address checked. A Zap that runs 300 times a month uses 300 credits, and Zapier counts its own tasks separately.
Do I need a paid BounceIntel plan?
The Zap connects with an API key, and keys come with any paid plan, monthly or a one-off pack. The 100 free credits on signup can be used in the dashboard to test verdicts on your own addresses first.
More integrations
Other apps teams pair with it
HubSpotCRM and salesEvery new or edited HubSpot contact gets its email checked against the receiving mail server, and the verdict lands on the contact record where your workflows can use it.
Open
Zoho CRMCRM and salesEach lead created in Zoho CRM has its email checked against the receiving mail server, so follow-ups, cadences and campaigns start from addresses that exist.
Open
PipedriveCRM and salesNew persons in Pipedrive get their email checked as they are added, so deals are attached to people your team can actually reach.
Open
Salesforce is a trademark of its owner, used here only to identify the app. BounceIntel is not affiliated with or endorsed by Salesforce. The connection runs through Zapier.
Verify Salesforce emails before they bounce.
Connect BounceIntel in Zapier and every new address gets a verdict your next step can act on.