Enrich new senders
When a new email arrives in Gmail, enrich the sender 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.
Gmail Explore Gmail →
TriggersFires when a new email arrives in Gmail.
Fires when an email is sent from Gmail.
Fires when a tracked email sent via Gmail is opened.
Fires when an email sent via Gmail bounces.
Sends an email via Gmail.
Creates a draft email in Gmail.
Applies a label or folder to an email in Gmail.
Moves an email into a different folder in Gmail.
More Hunter + Gmail workflows
Find missing addresses
When a contact lacks an email, find one with Hunter and send the email from Gmail.
See details
See all Hunter + Gmail integrations → · Browse the full workflow library →
Common questions
Can Knit build “Enrich new senders” between Hunter and Gmail?
Yes — describe it in the box above and Knit's Integrations Agent researches Hunter and Gmail'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 email senders be enriched?
Yes. When a new email arrives in Gmail, Hunter can enrich the sender with company and role.
Can Hunter find emails for outreach?
Contacts found in Hunter can receive emails sent through Gmail.