Enrich new contacts
When a contact is created in Kylas, enrich it with Hunter.
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.
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.
Kylas Explore Kylas →
TriggersFires when a new contact or lead is added to Kylas.
Fires when a field on a contact changes in Kylas.
Fires when a deal, case or record moves to a new stage in Kylas.
Fires when a deal is marked won in Kylas.
Creates or updates a contact in Kylas.
Creates a new deal in Kylas.
Moves a deal or record to a new stage in Kylas.
Logs a call, email, or note against a record in Kylas.
More Hunter + Kylas workflows
See all Hunter + Kylas integrations → · Browse the full workflow library →
Common questions
Can Knit build “Enrich new contacts” between Hunter and Kylas?
Yes — describe it in the box above and Knit's Integrations Agent researches Hunter and Kylas'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 new contacts be enriched?
Yes. When a contact or company is created in Kylas, Hunter can add title, company size and verified email.
Can prospects go straight into the CRM?
New contacts or companies found in Hunter can be created in Kylas with their enriched fields.