When payment refund in Zoho Checkout, sync it to Givebutter.
When a payment refund occurs in Zoho Checkout, update donor records in Givebutter.
See all Zoho Checkout + Givebutter integrations or talk to a human
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.
Zoho Checkout Explore Zoho Checkout →
TriggersFires when a new customer is created in Zoho Checkout.
Fires when a subscription is canceled in Zoho Checkout.
Fires when a new invoice is generated in Zoho Checkout.
Fires when a payment attempt fails in Zoho Checkout.
Creates a new customer in Zoho Checkout.
Creates a new subscription in Zoho Checkout.
Cancels an existing subscription in Zoho Checkout.
Updates a customer's billing details in Zoho Checkout.
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.
Enterprise-grade security
Common questions
Can Knit build “When payment refund in Zoho Checkout, sync it to Givebutter.” between Zoho Checkout and Givebutter?
Yes — describe it in the box above and Knit's Integrations Agent researches Zoho Checkout 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.