Enrich new subscribers
When someone subscribes in lemlist, enrich them with Hunter.
Google for Startups AcceleratorHow 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.
Hunter Explore Hunter →
TriggersFires when Hunter finds or captures a new lead.
Fires when a new contact is added to a list in Hunter.
Fires when a new company matches a saved search in Hunter.
Adds job title, phone and company data to a contact with Hunter.
Looks up firmographic data for a company with Hunter.
Finds and verifies a prospect's work email with Hunter.
lemlist Explore lemlist →
TriggersFires when a new subscriber is added in lemlist.
Fires when a contact unsubscribes in lemlist.
Fires when a subscriber opens or clicks a campaign in lemlist.
Creates or updates a subscriber in lemlist.
Unsubscribes a contact in lemlist.
Adds a subscriber to a list or segment in lemlist.
Sends a one-off transactional email via lemlist.
More Hunter + lemlist workflows
See all Hunter + lemlist integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Enrich new subscribers” between Hunter and lemlist?
Yes — describe it in the box above and Knit's Integrations Agent researches Hunter and lemlist'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 prospects be added to a list?
Yes. Contacts found in Hunter can be added as subscribers in lemlist.
Can subscribers be enriched?
When a subscriber joins in lemlist, Hunter can add company and role data for segmentation.