When deal moved to new stage in Gust, sync it to Stripe (Legacy).
Monitor Gust for when a deal moves to a new stage. Whenever a stage change occurs, update or sync the corresponding deal details to Stripe (Legacy).
See all Gust + Stripe (Legacy) 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.
Gust Explore Gust →
TriggersFires when a new donation, pledge or investment is recorded in Gust.
Fires when a donor sets up a recurring gift in Gust.
Fires when a fundraising campaign or round in Gust hits its goal.
Creates or updates a donor or investor record in Gust.
Sends a donation receipt via Gust.
Starts a new fundraising campaign in Gust.
Stripe (Legacy) Explore Stripe (Legacy) →
TriggersFires when a new customer is created in Stripe (Legacy).
Fires when a subscription is canceled in Stripe (Legacy).
Fires when a new invoice is generated in Stripe (Legacy).
Fires when a payment attempt fails in Stripe (Legacy).
Creates a new customer in Stripe (Legacy).
Creates a new subscription in Stripe (Legacy).
Cancels an existing subscription in Stripe (Legacy).
Updates a customer's billing details in Stripe (Legacy).
Common questions
Can Knit build “When deal moved to new stage in Gust, sync it to Stripe (Legacy).” between Gust and Stripe (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches Gust and Stripe (Legacy)'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.