When email replied in Hunter, sync it to Copper.
When an email is replied to in Hunter, update activity status in Copper.
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.
Copper Explore Copper →
TriggersFires when a new contact or lead is added to Copper.
Fires when a field on a contact changes in Copper.
Fires when a deal, case or record moves to a new stage in Copper.
Fires when a deal is marked won in Copper.
Creates or updates a contact in Copper.
Creates a new deal in Copper.
Moves a deal or record to a new stage in Copper.
Logs a call, email, or note against a record in Copper.
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.
More Copper + Hunter workflows
See all Copper + Hunter integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When email replied in Hunter, sync it to Copper.” between Copper and Hunter?
Yes — describe it in the box above and Knit's Integrations Agent researches Copper and Hunter'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 Copper, 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 Copper with their enriched fields.