Verify your Freshsales contacts before you send
SimpleVerifier has no Freshsales connector or marketplace app. The working route is a CSV round trip: export your contacts, verify the file, then import it back as an update so each contact carries its result.
The workflow
- Export the contacts. Freshsales documents a full-account export under Admin Settings > Account Settings > Account Settings > Export data: pick the period and the records (contacts are one choice), click Export, and a zip file is emailed to you. You can export up to five times a day, and the full time range only once.
- Upload the CSV on the verify page, signed in; the first 100 checks are free. The email column is found by its header or contents and every other column is kept.
- When the job finishes, download the valid, risky and invalid files. Each keeps all of your original columns.
- Create a custom contact field for the result first (for example Email status), so the import has somewhere to put it.
- Go to Contacts, use the import button and choose Import from CSV/XLSX, then upload the file. Freshsales wants a header row and a file under 5 MB.
- In the mapping step map the email column, map the result column to your custom field, and choose Update only your existing records with Email as the identifier, so no new contacts are created. Email is matched against the contact's primary email only.
- Build a list or filter on your custom field (for example Email status is not invalid) and send campaigns only to that.
Menu names follow Freshsales’s own help articles, checked 21 Nov 2026: export all data, import contacts from CSV/XLSX. Vendors rename menus, so trust what you see on screen if it differs. SimpleVerifier is not a Freshsales partner and has no Freshsales connector.
Columns to map
- Email, used as the identifier; only the primary email of a contact is matched.
- A custom field for the result. Fields can be mapped once each, so do not map the same column twice.
- Leave the Owner column unmapped unless you want ownership to change.
What to do with risky and catch-all results
Risky contacts are mostly catch-all domains and role addresses. Keep them out of your first campaign, send them in a smaller batch later and watch the bounce rate before widening. Do not delete them from the CRM: the person may still be reachable by phone.
What people use it for
- Check a list of leads that came in from web forms before a Freshsales email campaign.
- Re-verify an old contact database before a sales sequence.
- Find invalid emails that make deal and contact data look healthier than it is.
Using the result
Each address comes back valid (the mail server confirmed the mailbox), risky (delivery could not be confirmed: a catch-all domain, a role address such as info@, or a provider that hides mailbox status) or invalid (it will bounce, or it is a throwaway address).
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Comparing tools? See email verifiers for Freshsales compared, with prices checked on each vendor’s site.
Run your 100 free checks on one list before you switch anything
Export one list’s addresses as a CSV and upload it: the first 100 are checked free in the dashboard, no card needed. Compare the results with what you use now, then decide. Nothing in Freshsales changes until you import a file back.
Common questions
- Which plans include API access for Freshsales?
- API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- Is there a SimpleVerifier app in the Freshworks marketplace?
- No. There is no Freshsales connector or marketplace listing; the CSV export and update-import above is the supported route.
- Will importing overwrite my contacts?
- Without the overwrite option Freshsales updates only fields that are empty, and the result column goes into a new field, so existing data is left alone. Test with a small file first.