In this article, we'll show you how to evaluate the Impossible Email Verifier in the best way (fastest, easiest, cheapest) depending on your use case.
IMPORTANT NOTE : if you are using the FREE Forever plan, batch jobs like CSV uploads and CRM sync will be heavily throttled to prevent abuse (read more here).
Creating a CRM Integration Job
Navigate to the CRM Integrations page and connect the relevant CRM Integration via Oauth
Navigate to the Email Verifier page and click the CRM Integration Option
Fill out the options, then click save to create your scheduled job (quickstart guide)
"Just-In-Time" Email Verification
The filtering capability of CRM Integration jobs creates opportunities to significantly improve email deliverability and lower costs.
For example, let's say you are loading contacts into your sequencing tool for an outbound campaign, and you want to lower the bounce rate by verifying all the imported emails. The campaign may take 3 months to get through, so a single bulk verification won't cut it (what if some of your contacts change jobs a month later?). This forces you to do verifications in batch over and over again, verifying contacts that won't be emailed for months.
Here's how you can solve this with CRM Sync:
Map a field on the contact to sequence status (eg: "sequence_started"). Make sure you've programmed a delay of a few hours into your sequence rules so that the email verifier has enough time to verify the emails in the background before the first email is sent.
Create a CRM Integration job in Kitt AI that specifically filters for this status. This will ensure that contacts that formally start a sequence will come through in the next scheduled API sync.
Create a workflow rule in the CRM that checks the verification result on the Lead/Contact record following an update. If the value is an invalid value, trigger an update on the Contact record that stops the sequence (eg: lead status: do not contact)