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