How to trigger Zaps for existing Give Lively donations

Give Lively's Zapier integration sends donation data to thousands of other apps the moment a donation is made. By default, a Zap only fires for donations that come in after you turn the Zap on — historical donations don't flow through.

If you need historical donations to trigger your Zap (for example, to backfill a CRM after setting up a new automation), you can use a small workaround that routes your prior donation data through a Google Sheet. This article walks through when the workaround applies and how to set it up.

When this applies

Use this workaround any time you need a Zap to fire on Give Lively donations that were received before the Zap was active. Common situations:

• You just built a new Zap and want past donations pushed into the destination app (Salesforce, HubSpot, Mailchimp, a Google Sheet, etc.).
• You're migrating to a new system and want to seed it with your full donation history.
• A Zap was paused, broken, or off for some period and you need to backfill the gap.

If you only care about future donations going forward, you don't need this — your existing Zap is already handling them.

Before you start: pick your export window

The single most important decision is the date range you'll export from Give Lively, because it determines whether you risk duplicates in your destination app.

• If you don't have a live Give Lively Zap running yet: export whatever range you want. There's no overlap to worry about — just remember to scope the range to the data you actually need.
• If your live Give Lively Zap is already running: end your export window the day before your live Zap was activated. Donations recorded after that date are already flowing through your live Zap, and including them in the backfill will send them to your destination a second time.
• If your live Zap was paused or broken for a stretch: export only the gap period — from the last donation that synced successfully to the date the Zap came back online.

If you're not sure exactly when your live Zap started or stopped working, check your Zap's run history in Zapier before exporting. It's also worth confirming what de-duplication your destination app does on its own — some CRMs match incoming records on email or external ID and will skip duplicates automatically, which gives you a safety net.

Keep your Zapier costs down

This workaround inherently requires one additional Zap (the Google Sheets one) and consumes one or more tasks per row processed. Two practical ways to keep both in check:

• Pause your live Give Lively Zap during the backfill. If you're at your plan's active Zap limit, turning the live Zap off while you build and run the Sheets-based Zap keeps your active Zap count at one — no upgrade required. Turn the Sheets Zap off and the live Zap back on once the backfill completes. New donations won't sync while the live Zap is paused, so plan the backfill for a quieter time and keep the window short.

Strip the backfill Zap to the minimum number of steps. Your live Give Lively Zap may have several action steps — formatters, lookups, "send welcome email," "post to Slack," and so on. The backfill Zap only needs the steps required to land the record correctly in your destination. Skip any steps that produce side effects you don't want replayed for historical donors (a welcome email sent for a donation made 18 months ago is rarely what you want), and drop formatters or lookups you don't need. Each step removed is one less task per row across the entire backfill.

How to set it up

1. Export your historical donations from Give Lively

In your Give Lively admin, open Reports and select Line Items (All) from the Data Reports menu. This report is the same underlying dataset that powers the Zapier integration, which makes it the closest possible match to what your live Zap normally consumes — order date, donor full name and email, frequency, gross and net amount, page name and type, order ID, and other donation-level fields.

Set the From and To dates to the export window you decided on above, click Apply, then click Export CSV.

Open the CSV and confirm the columns include every field your destination app will need before moving on. Anything missing here can't be mapped later.

For background on what the Line Items report contains, see Give Lively's post A powerful new donor data management tool: Line Items (All).

2. Put the export into a Google Sheet

Create a new Google Sheet and paste the CSV contents in. Keep the column headers in row 1 — Zapier reads those as field names. Don't reorganize columns once the data is in; Zapier expects a stable structure.

3. Build a new Zap using Google Sheets as the trigger

In Zapier, create a new Zap with:

• Trigger app: Google Sheets
• Trigger event: New Spreadsheet Row
• Spreadsheet: the sheet you just created
• Worksheet: the tab with your donation data

For the action step, set up the same destination as your live Give Lively Zap (e.g., "Create Contact in HubSpot"). Map the destination fields to the corresponding Google Sheet columns. This is the most error-prone step — double-check that name, email, amount, and any IDs are landing in the right places.

Test the Zap with a single row and confirm a donation lands correctly in the destination app before moving on.

4. Use "Transfer existing data" to push every row through

Once the Zap tests cleanly:

1. In Zapier, open Transfers from the left nav.
2. Click Create Transfer and select the Zap you just built.
3. Choose the spreadsheet and worksheet, and confirm the rows you want to send.
4. Run the transfer.

Zapier will process each row through your Zap as if it had just been added. Progress and any errors show up in the Transfer dashboard.

5. Turn off the Sheets-based Zap when you're done

After the backfill is complete, turn off (or archive) the Google Sheets Zap so it doesn't keep firing if you edit the Sheet later. Your live Give Lively Zap continues handling new donations as it always has.

Things to watch for

Duplicates. Even with a carefully scoped export window, it's worth spot-checking your destination app for duplicates after the transfer completes — especially around the boundary date between your backfill and your live Zap. If you spot duplicates, most destination apps let you bulk-merge or delete by date range.

Field mapping drift. The Google Sheets trigger doesn't expose the same field names as the Give Lively trigger. Your Sheet-based Zap is essentially a separate Zap that happens to feed the same destination — treat it that way and re-verify every field mapping rather than assuming it matches your live Zap.

Zapier task usage. Every row processed through Transfer counts as a task on your Zapier plan. A 10,000-row backfill consumes 10,000 tasks (more if your Zap has multiple paid steps). Check your task quota before running a large transfer.

Tip: a phased approach for large backfills. For backfills of more than a few thousand rows, consider splitting the work into smaller batches — for example, one quarter or one month at a time — and running the transfer in stages. This makes it easier to catch mapping mistakes before they multiply, smooths your Zapier task usage across billing periods if you're near a quota, and gives you natural checkpoints to verify the data landed correctly in your destination before continuing.

Filters and multi-step logic. Replicate any filtering logic from your live Zap (e.g., "only donations over $50") so the backfill produces the same set of records your live Zap would have. For action steps, be more selective: keep formatters and lookups that are required for the destination action to work, but skip steps that fire side effects you don't want replayed for historical donors (welcome emails, Slack notifications, donor acknowledgments). Stripping those steps keeps the backfill consistent with what's already in your destination — and reduces task usage.

Need help?

For more on the Transfer feature itself, see Zapier's Transfer documentation. For questions about Give Lively exports or our Zapier integration, start with our getting started guide. If you run into any problems, contact our team by emailing support@givelively.org and with "Zapier Questions" in the title, or click on the chat box bubble on the bottom right of the screen.