When donation refunded/voided in Anedot, sync it to ShipStation.
When a donation is refunded or voided in Anedot, update the order status in ShipStation.
See all Anedot + ShipStation 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.
Anedot Explore Anedot →
TriggersFires when a new donation, pledge or investment is recorded in Anedot.
Fires when a donor sets up a recurring gift in Anedot.
Fires when a fundraising campaign or round in Anedot hits its goal.
Creates or updates a donor or investor record in Anedot.
Sends a donation receipt via Anedot.
Starts a new fundraising campaign in Anedot.
ShipStation Explore ShipStation →
TriggersFires when a new order or shipment is created in ShipStation.
Fires when a shipment is picked up, in transit or delivered in ShipStation.
Fires when a shipping label is created in ShipStation.
Creates a shipping or delivery order in ShipStation.
Creates a shipment and books the carrier in ShipStation.
Looks up the tracking status of a shipment in ShipStation.
Common questions
Can Knit build “When donation refunded/voided in Anedot, sync it to ShipStation.” between Anedot and ShipStation?
Yes — describe it in the box above and Knit's Integrations Agent researches Anedot and ShipStation'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.