When donation refunded/voided in Anedot, sync it to Constant Contact.
When a donation is refunded or voided in Anedot, update donor preferences in Constant Contact.
See all Anedot + Constant Contact 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.
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.
Constant Contact Explore Constant Contact →
TriggersFires when a new subscriber is added in Constant Contact.
Fires when a contact unsubscribes in Constant Contact.
Fires when a subscriber opens or clicks a campaign in Constant Contact.
Creates or updates a subscriber in Constant Contact.
Unsubscribes a contact in Constant Contact.
Adds a subscriber to a list or segment in Constant Contact.
Sends a one-off transactional email via Constant Contact.
Enterprise-grade security
Common questions
Can Knit build “When donation refunded/voided in Anedot, sync it to Constant Contact.” between Anedot and Constant Contact?
Yes — describe it in the box above and Knit's Integrations Agent researches Anedot and Constant Contact'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.