Donorbox

Bring Donorbox fundraising data into your workflows. Agents list donations, donors, campaigns, and recurring plans, and log offline gifts so donation data flows into CRMs, spreadsheets, and accounting tools.

5 actions Basic auth available

Donorbox website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The nightly reconciliation run starts after the day's batch closes

List Donations pulls the day's gifts with amount, status, donor, and campaign

List Plans checks recurring subscriptions for failed or lapsed payments in the same window

Agent matches each donation against the accounting ledger and flags gifts that appear in one system but not the other

The finance lead reviews the unmatched items, because writing a correcting entry into either system without understanding why they diverged hides the error instead of fixing it

Create Donation logs approved offline gifts, the checks from the gala, so they sit alongside online giving

The reconciliation summary posts to the team with matched totals and resolved exceptions

What This Integration Enables

Nonprofit finance runs on trust, and trust runs on records that agree. Donorbox holds the giving data; the CRM, the mail platform, and the accounting system each hold a partial copy that drifts. This connector puts FlowRunner agents on the drift: they list donations with full filtering by campaign, donor, and date, pull donor records with lifetime totals, track campaign progress against goals, monitor recurring plans, and log offline gifts so the online record becomes the complete record. The position behind the design: donation data is financial data, and it deserves financial-data discipline. Reads flow freely into reporting and outreach; the one write, Create Donation, is a ledger entry and gets treated like one. This matters more for nonprofits than for most businesses, because the people reading the numbers are not employees. Boards, auditors, grantmakers, and major donors all form judgments from giving data, and a development office of two cannot staff a nightly reconciliation. FlowRunner agents can. The same flows that keep the ledger clean also feed stewardship: the thank-you that goes out while the gift is still fresh, the lapse call that happens before the donor has mentally moved on, the milestone alert that reaches the team while the campaign can still act on it. - Reconcile donations against the accounting ledger on a schedule - Sync donors with lifetime totals and last-gift dates into CRM and email audiences - Watch campaign progress and alert on milestones - Sweep recurring plans for failures, lapses, and upcoming renewals - Log offline gifts with campaign and donor attribution

Without FlowRunner

Two versions of the truth Donorbox says one total, the accounting ledger says another, and someone spends Friday finding out why

Offline gifts live in a drawer Checks and cash from events get deposited but never join the donor's giving history

Lapsed donors go quiet unnoticed A failed recurring payment surfaces months later as a smaller year-end number

With FlowRunner

One reconciled record Donations flow to the ledger nightly, and only genuine exceptions reach a human

Every gift counts once, everywhere Offline donations are logged with campaign and donor attribution the week they arrive

Lapses surface in days Plan sweeps flag failed and expiring subscriptions while a warm phone call can still save them

Use Case Scenarios

The nightly ledger sync

Each night, List Donations pulls the day's gifts newest first and appends them to [Google Sheets](/integrations/google-sheets) for the development team, while matching entries land in [QuickBooks Online](/integrations/quickbooks) as payments. Amount or attribution mismatches go to an exception queue instead of being force-matched. The audit at year end starts from a ledger that has been reconciling itself every 24 hours, not from a shoebox of exports.

Stewardship segmented by real giving history

Weekly, List Donors pages through supporters with their lifetime totals, donation counts, and last-gift dates, and syncs them into [Mailchimp](/integrations/mailchimp) audience segments: first-time givers get the welcome series, five-year donors get the impact report, and donors whose last gift is aging get the reconnection note. The segmentation reflects what people actually gave, not what a stale export said in March.

The recurring revenue watchtower

A daily sweep of List Plans filters for plans whose status changed or whose next scheduled donation has slipped. High-value lapses post to [Slack](/integrations/slack) with the donor's history attached so the development director can call personally. Meanwhile List Campaigns runs against active campaigns, and when total raised crosses 90 percent of goal, the team hears about it the same hour, in time to plan the final push rather than read about it afterward.

Human-in-Loop Highlight

Create Donation writes a financial record that propagates everywhere giving data goes: the donor's lifetime total, the campaign's raised amount, the year-end tax receipt, the number the board reads. An offline gift logged twice, or attributed to the wrong donor, is not a display bug; it is a misstated acknowledgment letter and a reconciliation break someone will chase for hours. So FlowRunner flows never let an agent post offline gifts straight through. The agent drafts the entry, campaign, amount, donor identity, date, source of the record, and the finance lead confirms it against the deposit: "Log $2,500 check from the Hendersons to the Capital Campaign, dated July 14, from the gala batch?" Approved entries post in seconds. The judgment about what belongs in the giving record stays with the person who signs the reconciliation, and the approval itself becomes part of the audit trail: who confirmed the entry, when, and against which deposit.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Donations

List Donations Retrieves donations, most recent first by default, filtered by campaign, donor, email, name, date range, and amount range, with page-based pagination. Returns amount, status, donor details, and campaign. The read behind reconciliation and reporting.
Create Donation Creates a donation record for an existing campaign, attributed to a donor. Used to log offline gifts, cash, checks, externally processed payments, so they appear alongside online giving. The ledger write FlowRunner gates with approval.

Donors

List Donors Retrieves supporters with contact details, lifetime totals, donation counts, and last donation dates, filterable by name and email. The source for CRM sync and stewardship segmentation.

Campaigns

List Campaigns Retrieves fundraising campaigns with goal amount, total raised, donation count, currency, and public slug. The progress feed behind milestone alerts.

Plans

List Plans Retrieves recurring donation plans with amount, frequency, status, payment method, and next scheduled date, filterable by campaign, donor, and date range. The sweep target for lapse detection and renewal forecasting.

Frequently Asked Questions

What can FlowRunner do with Donorbox?

FlowRunner agents can run List Donations, Create Donation, and List Donors in Donorbox, plus 2 more actions.

Does connecting Donorbox to FlowRunner require OAuth?

No. Donorbox connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Donorbox trigger a FlowRunner workflow automatically?

Donorbox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Donorbox

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us