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