Have companies identified by Snitcher enter your CRM as Leads instead of Accounts, so they land in your sales team's existing qualification process.
Why it matters?
Many sales teams do not want companies identified by Snitcher to show up as fully formed Accounts right away, because their process runs new prospects through a Lead stage first for qualification.
Skipping straight to an Account bypasses that process and can create messy, premature records. Lead Flow makes Snitcher enter that same Lead stage instead, so identified companies land in your sales team's existing qualification workflow.
Prerequisites
Lead Flow is available on Salesforce, Zoho CRM, and Microsoft Dynamics. It is not available for Pipedrive.
There is no plan or permission restriction. Lead Flow is available to every account regardless of plan.
Setup steps
Go to Settings > Integrations and open your connected CRM's configuration page.
Turn on the Lead flow toggle. You will see the description "Match identified companies to CRM leads before accounts."
A Leads tab appears next to your other object tabs. Review the default lead field mappings and adjust them if needed (see Settings and options below for the full defaults per CRM).
Turning this on triggers a full re-sync of your integration. This runs in the background and can take a while depending on the size of your workspace.
đ¨ If you have unsaved field mapping changes elsewhere on the page, save or discard them first. The Lead flow toggle is locked until you do.
What this means for you?
With Lead Flow on, each time Snitcher syncs a company it checks your CRM in this order:
If a matching Account already exists, Snitcher links to that Account. No Lead is created.
Otherwise, if a matching Lead already exists, Snitcher links to and updates that Lead.
Otherwise, Snitcher creates a new Lead using your lead field mappings.
Contacts follow the same logic.
If the company is linked to an Account, its contacts sync as normal CRM Contacts. While the company is in Lead state, each synced contact becomes its own Lead record instead, since CRM Leads represent a person and a company together.
This is also why the Lead field mapping includes company level fields alongside person fields, a Contact sent as a Lead needs both.
Lead conversion is tracked automatically.
When you convert a Lead in your CRM, Snitcher detects it and re-links the company to the resulting Account. If an Account with the same website later appears in your CRM some other way, Snitcher automatically upgrades the company's link from the Lead to that Account.
đĄ Switching back to Standard removes Snitcher's links to your Lead records, but does not delete the Lead records themselves from your CRM.
â
Your integration then runs a full re-sync against Accounts and Contacts instead.
Settings and options
Sync flow can be set to Standard (the default) or Lead flow, per CRM integration, per workspace.
Lead field mappings are a separate set of mappings targeting your CRM's Lead object, editable from the Leads tab. Sensible defaults are pre-filled per CRM, and you can edit them at any time.
Salesforce default fields
Company, Website, Description, Industry, Street, City, State, Country, Postal Code, First Name, Last Name, Email, Phone, Title
Zoho default fields
Company, Website, Description, Industry, Street, City, State, Country, Zip Code, First Name, Last Name, Email, Phone, Title
Microsoft Dynamics default fields
Company name, Website URL, Description, Address (line, city, state or province, country, postal code), First name, Last name, Email address, Telephone, Job title
Example
Say your sales team wants companies identified by Snitcher to enter your existing lead qualification process, rather than appearing as fully formed Accounts right away.
You turn on Lead Flow. From then on, Snitcher creates a Lead for each new company instead of an Account, letting your team qualify it through your normal process before it becomes an Account.
Things to know
Lead Flow is only available for Salesforce, Zoho CRM, and Microsoft Dynamics. It is not supported for Pipedrive.
Accounts always win. If a matching Account exists, Snitcher never creates a Lead for that company, and any existing Lead link is upgraded to the Account.
Changing your sync flow triggers a full re-sync of the integration. On larger workspaces this can take a while, since it runs as a background job.
While a company is in Lead state, every synced contact creates its own Lead record. This can look like several Leads for one company, that is expected behavior, not a duplicate.
Switching Lead Flow back to Standard does not delete anything in your CRM, it only removes Snitcher's links. Previously lead synced companies show as unsynced until the next re-sync matches them to Accounts.
Troubleshooting
The Lead flow toggle is not visible.
Your connected CRM does not support Lead Flow, or no CRM is connected yet. Lead Flow is only available for Salesforce, Zoho CRM, and Microsoft Dynamics.
The toggle is disabled with a message about unsaved changes.
Save or discard your other field mapping changes first, then the toggle unlocks.
A company synced to an Account when you expected a Lead.
A matching Account already existed in your CRM. Snitcher matches by your CRM's link field, typically the website domain.
Wondering when a Lead's link updates after you convert it in your CRM.
Snitcher updates the link automatically. Timing can vary a little depending on your CRM's own sync cadence.