Cancel Commitment
Updated today
Use Cancel Commitment in Zapier to end and archive an existing Gratona recurring commitment. If it has a linked sponsorship, the action ends that sponsorship as well and preserves its history.
If several active commitments belong to the same sponsorship, ending it archives all of them.
This action changes the Gratona commitment. Any recurring billing managed directly by another system or payment provider must also be cancelled in that system.
Before you start
Connect your Gratona account in Zapier. The marketplace listing may use the legacy name HelpYouSponsor.
Have the Gratona Commitment ID for the commitment you intend to end. Save it from the creation action or New Sponsorship or Recurring Donation trigger on the matching external recurring record.
Your connected Gratona user must have access to end the commitment.
Choose a unique reference that identifies this specific cancellation occurrence.
See Connect Gratona to Zapier for account setup.
Set up the action
Add a trigger for the external recurring record's cancellation or departure workflow.
Add a filter so only records that should end in Gratona continue. Do not cancel a continuing sponsorship simply because another field was edited.
Add a Gratona action and choose Cancel Commitment.
Select the connected Gratona account.
Map Commitment ID and Cancellation Reference.
Test with a commitment you intend to end, review the archived result in Gratona, and publish the Zap when the result is correct.
Testing this action archives the actual commitment and ends its linked sponsorship. Confirm the target before selecting Test step.
Fields to map
Zapier field | What to enter |
|---|---|
Commitment ID — required | The Gratona Commitment ID stored on the external recurring record. Do not use its Salesforce ID or the Gratona Sponsorship ID. |
Cancellation Reference — required | A unique reference for this cancellation, up to 191 characters. Combine the external recurring record ID with its saved change version or timestamp, for example RD-1001:cancel:3. |
Keep the reference unchanged on retries. Use a saved source value rather than the Zap's current run time.
What the result means
The result includes the Commitment ID, linked Sponsorship ID when present, Status, Archived, Cancellation Date, and Cancellation Event ID when a captured archive event is available.
Use Commitment ID to update the matching external record. The Cancellation Event ID identifies the individual archive event and can help prevent processing that same cancellation twice.
If the commitment is already archived, the action succeeds without cancelling it again or creating another archive event. The Cancellation Event ID may be empty for an older archive with no captured event.
Retries and a later cancellation
An exact retry with the same Commitment ID and Cancellation Reference returns the original result. It does not add a duplicate cancellation event. If the commitment was restored after the original cancellation, that old retry does not end it again.
If a restored commitment needs to be cancelled again, use a new Cancellation Reference for the new occurrence. References are case-sensitive; reusing one with a different Commitment ID produces a conflict.
Transfers and recipient departures
This action ends a commitment; it does not select a replacement recipient, create a replacement commitment, or archive the recipient record. Edit Entity only updates recipient fields and does not perform the sponsorship archive or transfer workflow.
For a continuing sponsorship, review Reassign a sponsorship. For a recipient departure, review Record a reason when a recipient leaves or a sponsorship ends.
Troubleshooting
Commitment not found or access denied: Check the Gratona Commitment ID, connected workspace, and user's access.
Reference conflict: Reuse the same reference and target for a retry. Use a new reference for a genuinely new cancellation occurrence.
External charges continue: Review the recurring schedule in the external billing system; ending the Gratona commitment does not cancel that schedule there.