Updated Donation
Updated last week
Use Updated Donation to keep an existing destination gift in sync after a donation is edited in Gratona. Use New Donations for the workflow that first creates or matches the gift.
Set up the trigger
Choose the Gratona integration in Zapier, which may still be listed as HelpYouSponsor.
Select Updated Donation and connect the Gratona account that has access to the gifts you need.
Test the trigger and select a relevant edited donation sample.
Find the destination transaction using the mapping saved for its Gratona Donation ID.
Update the mapped transaction's fields, test one edit, then enable the Zap.
Reuse the original Donation ID
The top-level id identifies an update event and changes on later edits. Donation ID identifies the underlying allocation. Store the destination transaction ID against Donation ID and reuse that mapping on every update.
For example, changing a gift's date should update that mapped gift's date. A new update-event ID must not create a second financial transaction. If there is no verified destination mapping, route the record for review or an explicit find-and-match step before creating anything.
Map source, recognition and dates
This trigger exposes the same giving-source, DAF disclosure, advisor, IRA custodian, soft-credit, amount and date fields described in New Donations.
Direct: Donor ID is the financial owner. Reconcile any recorded soft-credit line items.
DAF: Donor ID is the sponsor organization. Use DAF soft-credit line items for advisor recognition and honor named, fund-only, anonymous or unrecorded disclosure.
IRA / QCD: Donor ID identifies the financial owner: the custodian institution on gifts recorded with custodian credit, and the IRA owner on older gifts that keep their saved attribution. Use the IRA owner fields and the soft-credit line items for the recognized person.
Use Individual Transaction Amount for this allocation. Payment Transaction Amount represents the whole payment.
Map Gift Date to the destination gift date and Deposit Date separately when supplied. Updated At is the allocation's change time.
Reconcile existing recognition entries instead of appending the same credit on every edit. An empty DAF advisor field is not proof that all soft-credit recognition should be removed; inspect the recorded soft-credit list and disclosure.
Verify the result
Edit a gift that already has a destination mapping. Confirm that the same transaction is updated, its financial owner remains correct, recognition is not duplicated, and Gift Date and Deposit Date remain independent. Check the Zap run output and the destination record before enabling bulk workflows.
Changing Giving Source does not replay a previously consumed New Donations event. Adding or editing a soft credit by itself does not trigger Updated Donation. If the gift is later edited, its update includes the current soft-credit details. Turning on a Zap does not automatically backfill historical gifts.