Log reviews on contacts
When a new review arrives in pulseM, update the contact in Leap.
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.
Leap Explore Leap →
TriggersFires when a new contact or lead is added to Leap.
Fires when a field on a contact changes in Leap.
Fires when a deal, case or record moves to a new stage in Leap.
Fires when a deal is marked won in Leap.
Creates or updates a contact in Leap.
Creates a new deal in Leap.
Moves a deal or record to a new stage in Leap.
Logs a call, email, or note against a record in Leap.
pulseM Explore pulseM →
TriggersFires when a customer leaves a new review in pulseM.
Fires when a review is edited or answered in pulseM.
Fires when a customer answers a feedback survey in pulseM.
Invites a customer to leave a review with pulseM.
Adds or updates a customer contact in pulseM.
Posts a public reply to a review in pulseM.
More Leap + pulseM workflows
See all Leap + pulseM integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Log reviews on contacts” between Leap and pulseM?
Yes — describe it in the box above and Knit's Integrations Agent researches Leap and pulseM'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 a closed deal trigger a review request?
Yes. When a deal is won or a contact reaches a stage in Leap, pulseM can send a review request.
Can reviews be logged on contacts?
When a review arrives in pulseM, the matching contact in Leap can be updated with the rating.