Verify new leads
When a new lead is added in SalesQL, verify the email with mailfloss.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
mailfloss Explore mailfloss →
TriggersFires when a list or bulk verification job finishes in mailfloss.
Checks whether an email address is valid and deliverable with mailfloss.
Runs a bulk verification on a list of addresses in mailfloss.
Returns the remaining verification credits in mailfloss.
SalesQL Explore SalesQL →
TriggersFires when SalesQL finds or captures a new lead.
Fires when a new contact is added to a list in SalesQL.
Fires when a new company matches a saved search in SalesQL.
Adds job title, phone and company data to a contact with SalesQL.
Looks up firmographic data for a company with SalesQL.
Finds and verifies a prospect's work email with SalesQL.
More mailfloss + SalesQL workflows
Re-check enriched contacts
When a contact is enriched in SalesQL, verify the email again with mailfloss.
See details
See all mailfloss + SalesQL integrations → · Browse the full workflow library →
Common questions
Can Knit build “Verify new leads” between mailfloss and SalesQL?
Yes — describe it in the box above and Knit's Integrations Agent researches mailfloss and SalesQL's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can found emails be verified?
Yes. When SalesQL finds or enriches a contact email, mailfloss can verify it.
Why verify enriched emails?
Enrichment data can go stale; verification in mailfloss catches addresses that would bounce.