BetterWorld + Zapier: Route Registrations vs Donations

Route BetterWorld registrations and donations into separate Zapier paths: pick the right trigger, branch on campaign type, and fix empty trigger tests.

Nov 16, 2026
BetterWorld + Zapier: Route Registrations vs Donations
To route registrations and donations into separate paths with the BetterWorld Zapier integration, trigger on New or Updated Transaction and branch on the campaign type that comes with each transaction. BetterWorld's transaction data has no field that says "registration" or "donation", so you build the split from campaign data, payment fields, and a lookup table for anything that doesn't fit.

What you're trying to automate

Most nonprofits running events and campaigns on BetterWorld want two separate Zapier paths:
  • Donations: update the donor record, send the receipt, and notify the development team.
  • Registrations: add the participant or fundraiser to the event roster or registration workflow.
BetterWorld sends both to Zapier as transactions, so the Zap needs a rule for telling them apart.

Step 1: Pick the right BetterWorld Zapier trigger

The BetterWorld app on Zapier has three triggers: New or Updated Campaign, New or Updated Supporter, and New or Updated Transaction (as of November 2026, check the BetterWorld app page on Zapier for changes). Use Transaction. BetterWorld documents it as the trigger for donation, ticket, giveaway, and auction purchase data.
If your Zap runs on New or Updated Campaign, switch it. That trigger fires when a campaign is created or edited, not when someone gives or signs up. Before you build the registration path, confirm with BetterWorld support that your registration type creates a transaction, especially free registrations with no payment attached.

Step 2: Fix "no transactions found" in the trigger test

When the trigger test comes back empty, work through these in order:
  1. Reconnect the BetterWorld account in the trigger step, then test again.
  2. Create fresh activity. Make a small test donation and a test registration in BetterWorld so there are new records to pull.
  3. Re-test the trigger after those records exist. Zapier only offers the fields that appear in its sample data, so an old or empty sample hides fields you need.
  4. Build the trigger in a new Zap instead of a duplicated one. That rules out a stale copied configuration.
  5. If the test is still empty, send BetterWorld support a screenshot of the result and ask whether polling delays or account settings are blocking it.

Step 3: Find the field that separates registrations from donations

The transaction payload doesn't include a transaction type. It does include a campaign object with the campaign's type, and BetterWorld lists these types: auction, donation, impact campaign, crowdfunding campaign, paddle raise, peer-to-peer, ticketing, and giveaway (per BetterWorld's Zapier field mapping guide, November 2026).
If your registrations happen in ticketing or peer-to-peer campaigns and your donations come through donation campaigns, campaign type is your routing field. A few other transaction fields help with edge cases:
  • gross_amount: useful when your registrations are free and your donations never are.
  • frequency: separates recurring gifts from one-time gifts.
  • payment_status: Succeeded, Pending, Failed, or Refunded. Stop failed and refunded payments before either path runs.
  • Campaign ID or title: works when you need a rule for one specific campaign.

What to ask BetterWorld support

If one campaign collects both registrations and donations, campaign type won't split them. Ask BetterWorld support three things:
  • Do registrations in our campaign create transactions in the Zapier trigger?
  • Is there a field in the transaction data that separates a registration fee from a donation?
  • If not, what do other organizations use to tell them apart?
Send this as its own ticket, separate from any "no transactions found" problem. Two clear questions get two clear answers.

Step 4: Build the routing in Zapier

Option A: One Zap with Paths on campaign type

This is the structure we start with. One trigger catches every transaction, and the Zap splits from there:
  1. Trigger: BetterWorld, New or Updated Transaction.
  2. Filter: stop the Zap when payment status is Failed or Refunded.
  3. Path A (Donations): campaign type is donation. Add crowdfunding or impact campaign if you run those.
  4. Path B (Registrations): campaign type is ticketing or peer-to-peer.
  5. Fallback path: anything else goes to a review step, so nothing drops silently.
Paths with a fallback branch is the pattern we use on most Zapier routing builds. The fallback is what catches the campaign type you forgot existed.

Option B: Classify with a lookup table

When no field separates the two, keep a small classification table keyed by transaction ID or supporter ID. Airtable gives you views and an interface for the team; Google Sheets is the simplest option for non-technical staff.
  1. Trigger: New or Updated Transaction.
  2. Look up the transaction ID in the table.
  3. If it's found, use the stored type (registration or donation) to pick the path.
  4. If it isn't, add a row marked "unknown" and notify the team to set the type.
This puts a person in the loop for the cases the data can't decide, and the table shows you which rules you still need to write.

Option C: Trigger registrations from another source

If BetterWorld sends a registration confirmation email or another signal you can catch outside the transaction trigger, start the registration path from that. Email Parser by Zapier can turn a confirmation email into a trigger. The transaction Zap then handles donations only.

Common gotchas

  • Test data isn't always the newest record. Build with whatever sample loads, then check the first live runs in Zap history.
  • Updates fire the trigger too. A refund or edit sends the transaction again with trigger_event set to "updated". Filter on "created", or log transaction IDs, so a donor doesn't get two receipts.
  • Don't assume registrations and donations fill the same fields. Check a live sample of each before you map anything.
  • BetterWorld publishes a Zapier field mapping guide listing every field on each trigger. Check it before guessing at field names.

Get help building this

Routing BetterWorld transactions by type usually breaks on the edge cases: a campaign that takes both registrations and donations, or an update that sends a second receipt. If you're stuck there, book a ZoomFlow session and one of our consultants will build the routing with you live on the call.