When new lead in Hunter, sync it to awork.
When a new lead is identified in Hunter, create a task or project update in awork.
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.
awork Explore awork →
TriggersFires when a new task, job or item is created in awork.
Fires when a task in awork is marked complete.
Fires when a task's due date in awork is coming up.
Fires when a task, job or project changes status in awork.
Creates a new task, job or item in awork.
Updates a task's status or assignee in awork.
Posts a comment on a task in awork.
Assigns a task in awork to a team member.
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 awork + Hunter workflows
See all awork + Hunter integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When new lead in Hunter, sync it to awork.” between awork and Hunter?
Yes — describe it in the box above and Knit's Integrations Agent researches awork 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 prospects create tasks?
Yes. When a new lead or company is found in Hunter, awork can create a task for an owner.
Can tasks trigger enrichment?
When a task names a company or contact in awork, Hunter can enrich it.