Gmail integration
Verify the sender of new Gmail messages
When a message arrives in your inbox or under a label, the sender's address is verified, so you know which inbound leads and contacts are worth saving.
- Inbox and contacts
- No code
- Set up in minutes
The Zap
- 1
Trigger · GmailNew Email - 2
Action · BounceIntelVerify Email Address Verdict
SafeRiskyInvalidUnknown
- Starts from
- New Email
- BounceIntel step
- Verify Email Address
- You get back
- Verdict, score, reason and mailbox signals
- Zapier plan
- Any plan, including Free, for a two-step Zap
01Zaps
Start from a template
Each template opens in Zapier's editor with Gmail and BounceIntel already set up. Connect both accounts, check the field mapping, and turn it on.
Validate new Gmail emails with BounceIntel
New Email
Verify Email AddressValidate new labeled Gmail emails using BounceIntel
New Labeled EmailVerify Email AddressOr build your own
New EmailVerify Email AddressAny Gmail 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 Gmail emails
An inbox is a lead source that nobody cleans. Contact form notifications, replies to outreach and cold inquiries all land in Gmail, and many teams copy those senders straight into a CRM or a mailing list.
Not every sender address is one you can write back to later. Form notifications carry whatever the visitor typed, and some senders use aliases or throwaway inboxes. Verifying the sender before the address is saved anywhere keeps the contact list honest.
03Ideas
What to do with the verdict
The check on its own changes nothing. These are the steps that make it pay off inside Gmail.
Verify only a labelled folder
Use the labeled email trigger with a label such as Leads, set by a Gmail filter. Only those messages are checked, which keeps credit use predictable.
Save verified senders to a sheet
After the check, add a row to Google Sheets with the sender, verdict and score. It becomes a running log of inbound contacts you can import anywhere.
Flag suspicious inbound mail
When the sender comes back invalid or disposable, apply a Gmail label such as Check sender. It is a quick signal on messages that ask for payment or credentials.
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 Gmail
In Zapier, choose Gmail as the trigger app and pick New Email, 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 Gmail 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 Gmail.
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
Gmail and BounceIntel: common questions
Which address is verified, the sender or the reply-to?
Whichever you map. The template maps the sender, but for contact form notifications you usually want the reply-to address or the email written in the message body.
Will it use a credit on every email I receive?
On the new email trigger, yes. Most people use the labeled email trigger instead, so only the messages a Gmail filter marks are checked.
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
Microsoft OutlookInbox and contactsWhen a message arrives in your Outlook inbox or a shared mailbox, the sender's address is checked, so inbound leads are screened before anyone saves them.
Open
Google ContactsInbox and contactsNew and updated contacts have their email checked, so the address book your team relies on stays accurate.
Open
Microsoft ExchangeInbox and contactsWhen a new message arrives in an Exchange mailbox, the sender's address is checked, so inbound leads are screened before anyone saves them.
Open
Gmail is a trademark of its owner, used here only to identify the app. BounceIntel is not affiliated with or endorsed by Gmail. The connection runs through Zapier.
Verify Gmail emails before they bounce.
Connect BounceIntel in Zapier and every new address gets a verdict your next step can act on.