When refunded donation in Pledge, sync it to Constant Contact.
When a donation is refunded in Pledge, update the donor contact status in Constant Contact.
See all Constant Contact + Pledge 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.
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.
Pledge Explore Pledge →
TriggersFires when a new donation, pledge or investment is recorded in Pledge.
Fires when a donor sets up a recurring gift in Pledge.
Fires when a fundraising campaign or round in Pledge hits its goal.
Creates or updates a donor or investor record in Pledge.
Sends a donation receipt via Pledge.
Starts a new fundraising campaign in Pledge.
Common questions
Can Knit build “When refunded donation in Pledge, sync it to Constant Contact.” between Constant Contact and Pledge?
Yes — describe it in the box above and Knit's Integrations Agent researches Constant Contact and Pledge'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.