Resources · Zapier integration

Donorbox Zapier integrationAutomate Donorbox with Zapier.

The Donorbox Zapier integration only listens. It gives you 6 triggers, all instant, 0 actions and 0 searches: Donorbox tells Zapier about a gift, a donor or a ticket sale, and another tool does the work. It runs on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Donorbox Zapier integration does for a fundraising team

Connecting Donorbox to Zapier means each new or edited record in your fundraising account (a donation, a donor, a campaign, a plan, a ticket or a ticket purchase) can start an automation on its own. Donorbox only plays one role here: it is the app that raises the hand. Every follow-up happens in another tool.

Three results teams usually build first. A thank-you that leaves on time: New or Updated Donation hands the gift to your email tool the moment it lands, so no donor waits for a manual export. A donor file that stays in sync: New or Updated Donor pushes profile changes to the CRM your major-gifts officer actually uses. A guest list for the gala: New or Updated Tickets Purchase Transaction and New or Updated Ticket feed the check-in sheet your volunteers open at the door.

Now the part the app page skips. Zapier cannot write anything into Donorbox. There is no action to record an offline gift, edit a donor or open a campaign, and no search to look a donor up. If your plan depends on Zapier changing Donorbox, it will not work here, whatever plan you pay for.

The other catch sits in the names. Every trigger is New or Updated: it fires when a record is created and again each time someone edits it. A Zap that adds a row or a contact on every firing will stack duplicates. Pick actions that update or notify.

Comparing tools? The Donorbox Make integration covers the same app on Make.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Here, every trigger comes from Donorbox.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you. Donorbox offers none, so it lives in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Instant vs polling
An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer. All six Donorbox triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What a Donorbox Zap really costs

Short version: listening to Donorbox is free, doing something about it is what counts.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeOne trigger and one action
  • Donorbox triggers6, all instant
  • Premium appNo

The trigger never costs a task, however many gifts come in. Each action that succeeds counts once, so a two-action Zap eats twice as much as a one-action Zap, and an action that fails is not billed. Donorbox is not a premium app, so the free plan accepts it, with one wall: two steps only. Add a filter or a second action and you need a paid plan. The interval grid below governs polling triggers; all six Donorbox triggers are instant, so they skip it.

Connect

Connect your Donorbox account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Donorbox account linked once, then reused by every Zap that needs it.

  2. 02

    Pick Donorbox

    Type Donorbox in the search box of the dialog, select it, then click Add connection. You need an existing Donorbox account; Zapier does not create one for you.

  3. 03

    Sign in and grant access

    Log in to Donorbox in the tab that opens and allow Zapier into the account. If the campaigns you want to watch belong to someone else, make sure your login can read them first.

First Zap

Your first Zap: alert the team when a gift lands

GoalPost a message to the team chat when a donation in Donorbox matches the condition you set.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Donorbox as the app and New or Updated Donation as the event. Select the connection you made above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent donations of the account, so you map the next steps on a real gift instead of a blank form.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field to watch, the rule and the value. Pick a number rule for a number field, or the filter never passes.

  4. 04

    Add the action

    Pick your chat tool and its send-message event, then map the donation details into the text. Remember that an edit to the same donation fires the Zap again.

  5. 05

    Test, then Publish

    Test each step once and read what came back. Then Publish to switch the Zap on. With the filter, this Zap is multi-step and needs a paid plan.

Triggers

The six Donorbox triggers

6 events start a Zap when something happens in Donorbox, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New or Updated Campaign

Instant trigger

In Zapier“Add a new campaign. Can be used to update an existing campaign too.”

Starts your Zap when a fundraising campaign is created in Donorbox, and again whenever an existing campaign changes. You get the campaign as it stands at that moment, ready to pass on to another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping a shared campaign calendar or a board of open appeals up to date without anyone copying titles across.
Watch out
an edit counts as an event, so the action you pick should update an entry rather than add a fresh one.
2

New or Updated Donation

Instant trigger

In Zapier“Add a new donation. Can be used to update an existing donation too.”

The one most teams reach for: a gift arrives, or a gift already recorded is edited, and Zapier receives it straight away. Your next step can thank, notify or record without waiting for an export.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending a personal thank-you from your email tool, or pinging the development director when a gift meets a condition you set in a filter.
Watch out
a correction to a donation fires the Zap again, so a thank-you Zap can greet the same donor twice.
3

New or Updated Donor

Instant trigger

In Zapier“Add a new donor. Can be used to update an existing donor too.”

Watches the people rather than the money. A new donor profile, or a change to an existing one, reaches Zapier as soon as Donorbox records it, and your Zap can carry it to the system that holds your relationships.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
mirroring donor details into a CRM where your major-gifts officer plans calls and keeps notes.
Watch out
pair it with an action that updates the matching contact; creating one on each firing builds a pile of duplicates.
4

New or Updated Plan

Instant trigger

In Zapier“Add a new plan. Can be used to update an existing plan too.”

Fires on the plans in your Donorbox account: a new plan appears, or an existing one is modified, and the Zap receives it at once. Useful when the follow-up on a plan belongs to another team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
letting the finance lead know in chat that a plan changed, so nobody has to spot it by hand.
Watch out
Zapier cannot edit or cancel a plan in Donorbox; any change itself still happens inside Donorbox.
5

New or Updated Tickets Purchase Transaction

Instant trigger

In Zapier“Add a new event transaction. Can be used to update an existing event transaction too.”

Covers the money side of your events: someone buys tickets through Donorbox, or a purchase already on file is updated, and the whole transaction lands in Zapier immediately.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending the order to the person who reconciles event income, or alerting the event lead that tickets just sold.
Watch out
an edit to the purchase sends it through again, so a running income total should be updated, not added to.
6

New or Updated Ticket

Instant trigger

In Zapier“Add a new ticket. Can be used to update an existing ticket too.”

Works one level down from the purchase: each ticket created or edited in Donorbox reaches Zapier on its own, which is what a door list or a seating plan needs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
updating the guest list your volunteers open at check-in, one row per attendee rather than one per buyer.
Watch out
run a test first and read which details a ticket carries before you build the guest list around them.
When it breaks

When a Donorbox Zap breaks

Zapier attaches no help article to Donorbox, so what follows is Zapier's own behavior applied to this app.

Nothing exotic, but each of these has cost a fundraising team a confused morning. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.

  • Past donations never show up

    A Zap only reacts to what happens after you publish it. Gifts and donors recorded before that stay where they are; moving them is a one-off import.
  • The same gift fires twice

    Every Donorbox trigger is New or Updated. A correction or a typo fix on a donation sends it through the Zap again, with everything that follows.
  • A bulk import stalls the Zap

    When Donorbox suddenly reports a huge batch, after an import or a migration, Zapier's flood protection can hold it back until you review it.
  • A Zap that feeds itself

    If a step writes back where its own trigger watches, the Zap sets itself off again and again and burns through the task count fast.
Need help

Need help automating Donorbox with Zapier?

A person reads every message.

FAQ

Donorbox Zapier integration: common questions

01Is the Donorbox Zapier integration free?
Yes, Donorbox is not a premium app, so it runs on the free Zapier plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. For a single thank-you email per gift, free is enough; for anything that sorts or branches, budget for a paid plan.
02How many tasks does a Donorbox Zap use?
The Donorbox trigger itself uses none. Zapier only bills an action that completes successfully, one task each time. A Zap with one action costs one task per firing, a Zap with three actions costs three. Keep in mind that every Donorbox trigger also fires on updates, so a donation that is edited twice after it arrives can cost three runs instead of one. A failed action is not counted against your plan.
03Does Donorbox send data to Zapier in real time?
Yes. All six Donorbox triggers are instant: Donorbox calls Zapier the moment the event happens, and the Zap starts right away. The plan interval grid, which goes from 15 minutes on Free to 1 minute on Team and Enterprise, only applies to polling triggers, so it does not slow Donorbox down even on the free plan. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect Donorbox to Zapier?
An existing Donorbox account and a Zapier account. You open the Apps page in Zapier, click + Add connection, pick Donorbox, sign in in the tab that opens and grant access. If you want the Zap to watch campaigns or records that belong to a colleague, your login needs read access to them. The connection is made once and every Zap that uses Donorbox reuses it. When you then test a Donorbox trigger, Zapier brings back the three most recent records of the account, which is the quickest way to see that the connection works.
05Why does a Donorbox Zap run again when nothing new came in?
Because every Donorbox trigger is New or Updated. Editing a donation, a donor, a campaign, a plan, a ticket or a purchase counts as an event, and the Zap runs again with the edited record. That is handy for keeping another tool in sync, and a nuisance for anything that should happen once. Point those triggers at actions that update an existing entry or send a notice, and avoid actions that add a new record each time.
06What if the Donorbox action you need does not exist in Zapier?
On Zapier, it does not exist at all: Donorbox offers triggers only, with no action and no search. Anything that should change data inside Donorbox, like logging an offline gift or editing a donor, has to be done in Donorbox itself or through another route. What Zapier does well with Donorbox is the opposite direction: reacting to what happens there and pushing it to your email tool, CRM, chat or spreadsheet.
07Zapier, Make or n8n for Donorbox?
It depends on the criterion, not on a winner. If your need is to react to Donorbox events and you want the shortest setup with instant triggers on a free plan, Zapier covers it. If you plan multi-step flows on a tight budget, compare how each tool counts its runs. If you need to self-host or keep data on your own servers, that criterion points away from Zapier. Check which Donorbox operations each platform offers before you choose.