When new order in Revv, sync it to BenchmarkONE.
When a new order is completed in Revv, update lead records in BenchmarkONE.
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.
Revv Explore Revv →
TriggersFires when a new donation, pledge or investment is recorded in Revv.
Fires when a donor sets up a recurring gift in Revv.
Fires when a fundraising campaign or round in Revv hits its goal.
Creates or updates a donor or investor record in Revv.
Sends a donation receipt via Revv.
Starts a new fundraising campaign in Revv.
BenchmarkONE Explore BenchmarkONE →
TriggersFires when a new contact or lead is added to BenchmarkONE.
Fires when a field on a contact changes in BenchmarkONE.
Fires when a deal, case or record moves to a new stage in BenchmarkONE.
Fires when a deal is marked won in BenchmarkONE.
Creates or updates a contact in BenchmarkONE.
Creates a new deal in BenchmarkONE.
Moves a deal or record to a new stage in BenchmarkONE.
Logs a call, email, or note against a record in BenchmarkONE.
Common questions
Can Knit build “When new order in Revv, sync it to BenchmarkONE.” between Revv and BenchmarkONE?
Yes — describe it in the box above and Knit's Integrations Agent researches Revv and BenchmarkONE'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.