Commitment Cancelled/Archived
Updated 4 weeks ago
Use Commitment Cancelled/Archived as a Zapier trigger when a Gratona sponsorship or recurring commitment ends. For example, update the matching Salesforce recurring record or create an internal follow-up task.
The trigger reports captured cancellation events, including commitment and sponsorship archives and recipient archive workflows that end linked sponsorships. It does not fire just because Edit Entity changes a recipient field to Inactive.
Set up the trigger
Create a Zap and choose the Gratona integration. If the listing uses HelpYouSponsor, that is its legacy marketplace name.
Select Commitment Cancelled/Archived as the trigger event.
Connect your Gratona account with access to the relevant commitment records.
Optionally select Program, or leave it blank to monitor all accessible programs and campaigns in the workspace, including standalone cancellation events with no program.
Test the trigger and check the returned Commitment ID, Cancellation Event ID, program, and cancellation date.
Add the external update or follow-up action. Map Commitment ID to the external record that stores that Gratona ID.
Test the downstream mapping, then publish the Zap.
See Connect Gratona to Zapier for account setup.
Choose a program
Program is optional. Select one to limit the trigger to that program. Leave it blank to use one Zap across programs and campaigns, then use Zapier Filters or Paths with Program ID or Program Name to route the result.
Some standalone commitments have no Program ID or Program Name. Leave Program blank to include their accessible cancellation events, and route them using designation fields. Selecting a program excludes events with no program.
Important output fields
Output | How to use it |
|---|---|
Cancellation Event ID | A stable identifier for this individual archive event. Save it to avoid processing the same event twice. |
Commitment ID | The Gratona commitment that ended. Use it to find the matching external recurring record. |
Sponsorship ID | The linked donor-recipient relationship, when present. A standalone commitment may not have one. |
Cancellation Date | When the commitment was archived. |
Cancellation Reference | The source reference when supplied by a cancellation action. It may be empty for a manual archive. |
Donor, recipient, program, and designation fields | Context for mapping the event. Recipient fields describe a sponsorship; fund or campaign designation fields describe a recurring campaign gift. Program fields may be empty for a standalone commitment. |
Amount Per Charge, Frequency, and Status | The commitment's captured schedule and archived status. |
The event retains a snapshot of the commitment when it ended. Later restoration or edits do not change that historical event. Check the current commitment in Gratona if your next step depends on its current state.
How repeat cancellations work
Each actual archive has its own Cancellation Event ID. Restoring a commitment and then cancelling it again produces a new event for the same Commitment ID. Repeating cancellation while it is already archived does not produce another event.
When mapping an external workflow, use Commitment ID to identify the recurring record and Cancellation Event ID to identify the occurrence. Do not substitute the event ID for the commitment ID.
Timing and testing
This is a polling trigger. Zapier checks on its polling schedule, so the event may arrive after a delay that depends on the Zapier plan.
The trigger covers captured cancellation events; it is not a complete export of every historical archived commitment. Older archives with no captured cancellation event will not appear. A test may return an existing event. If there is no sample, archive an intended test commitment in Gratona, then test again. Creating that sample ends a real commitment, so use a test record.
Avoid synchronization loops
If one Zap cancels Gratona commitments from external changes and another sends Gratona cancellations back, update the existing external record and add a filter to skip records already in the intended state. Preserve the mapped Gratona IDs and event reference instead of creating another recurring record for every notification.