New Sponsorship or Recurring Donation
Updated today
Use New Sponsorship or Recurring Donation as a Zapier trigger when a new active Gratona sponsorship or recurring commitment is created. For example, create or update the matching Salesforce recurring record and save the Gratona Commitment ID on it.
The trigger covers recipient sponsorships and recurring campaign gifts with a linked sponsorship relationship. Standalone commitments without that link are not included. It reports the commitment, not a newly received donation or a successful charge.
Set up the trigger
Create a Zap and choose the Gratona integration. The marketplace listing may use its legacy name HelpYouSponsor.
Select New Sponsorship or Recurring Donation as the trigger event.
Connect your Gratona account with access to the relevant records.
Optionally select Program, or leave it blank to monitor programs and campaigns across the connected workspace.
Test the trigger and review the Commitment ID, donor, designation, amount, and frequency.
Add an action to create or update the matching record in your external system. Save Commitment ID and Sponsorship ID, when present, for future synchronization.
Test the downstream mapping, then publish the Zap.
See Connect Gratona to Zapier for account setup.
Choose a program
Select Program to restrict the trigger to one program. Leave it blank to use a single Zap for programs and campaigns, then branch with Zapier Filters or Paths using Program ID or Program Name.
Map the output
Output | How to use it |
|---|---|
Commitment ID | The stable Gratona commitment identifier. Save it on the external recurring record and use it for later cancellation. |
Sponsorship ID | The linked sponsorship relationship identifier. Keep it separate from the Commitment ID. |
Donor ID, Donor Name, and Donor Email | Identify the supporter. Map custom donor fields when you store an external contact ID in Gratona. |
Program ID and Program Name | Route records to the correct external program or campaign. |
Recipient ID and Recipient Name | Identify the recipient for a sponsorship. These may be empty for a recurring campaign gift. |
Fund / Campaign Designation and Designation Type | Identify the destination of a recurring campaign gift. Fund fields may be empty for a recipient sponsorship. |
Amount Per Charge and Frequency | Map the amount expected for each payment period and its recurrence. |
Monthly Equivalent Amount | Use when the external system needs a normalized monthly value. |
First Payment Date | The earliest qualifying payment linked to the commitment. It is empty until such a payment exists. |
Next Payment Date, Payment Method, and Is Non-Charging | Review the schedule and which system manages payment collection. |
Stored Commitment Amount may use a different amount basis for older records. Use Amount Per Charge with Frequency when mapping the recurring schedule; do not assume every stored amount is the amount due each period.
Timing and event behavior
This is a polling trigger, so detection follows Zapier's polling schedule. It reads the commitment's current active state when polled, rather than preserving a snapshot from creation. A commitment archived before Zapier detects it may not appear.
Zapier identifies new records by their Commitment ID. Editing, reassigning, or restoring the same commitment is not a separate creation event for a commitment the Zap has already seen.
Use Commitment Cancelled/Archived for endings and a donation trigger for received gifts. Testing may show an existing active record; that sample does not mean the Zap will import every historical commitment when enabled.
Avoid duplicate records
Use an external create-or-update workflow keyed by the stored Gratona Commitment ID. If external recurring records also create Gratona commitments through another Zap, add filters so a record created by synchronization is not sent back as another new creation.
For externally billed commitments, keep charge collection in the billing system that owns the schedule. This trigger does not initiate charges or confirm that a payment was received.