When export donations in Charidy, sync it to SMS.to.
When donations are exported in Charidy, trigger thank-you text messages via SMS.to.
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.
Charidy Explore Charidy →
TriggersFires when a new donation, pledge or investment is recorded in Charidy.
Fires when a donor sets up a recurring gift in Charidy.
Fires when a fundraising campaign or round in Charidy hits its goal.
Creates or updates a donor or investor record in Charidy.
Sends a donation receipt via Charidy.
Starts a new fundraising campaign in Charidy.
SMS.to Explore SMS.to →
TriggersFires when a new text message is received in SMS.to.
Fires when a new call comes in or out through SMS.to.
Fires when a call is missed in SMS.to.
Fires when a call recording finishes processing in SMS.to.
Sends a text message through SMS.to.
Starts an outbound call via SMS.to.
Creates or updates a contact in SMS.to.
Sends a recorded voice message via SMS.to.
Common questions
Can Knit build “When export donations in Charidy, sync it to SMS.to.” between Charidy and SMS.to?
Yes — describe it in the box above and Knit's Integrations Agent researches Charidy and SMS.to'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.