Introduction to Fundraise Up
The Fundraise Up integration on iPaaS.com keeps donations and donor records flowing automatically from Fundraise Up into the rest of your organization's systems — so stewardship, accounting, and reporting always see the same source of truth.
API Version Support
The integration uses the Fundraise Up API (v1). The API address and credentials are configured in your subscription's connection settings. See the Fundraise Up Connections and Settings and Fundraise Up API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Fundraise Up, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Fundraise Up
← iPaaS.com reads the data from Fundraise Up
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Fundraise Up when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Fundraise Up | Allow Initialization? |
Customer | ← | Supporter | |
Transaction | ← | Donation |
Supporters carry their addresses, and donations carry their designation and fee lines and their payment. Donations reach iPaaS.com within seconds by the Fundraise Up webhook, or otherwise on the poll schedule you set; the first poll on a new subscription brings in donation history.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.3. Notable releases, newest first:
Version | Release Notes |
1.0.3 (current) | Donations reach iPaaS.com within seconds through a Fundraise Up webhook, with the scheduled poll as a backstop. Refunds, status changes, edits and recurring plan changes made in Fundraise Up after a donation is created now update its iPaaS.com Transaction, by webhook or on the next poll. Each recurring installment carries its plan's current status, frequency, installment number and dates. A processing fee the donor covers can arrive as its own fee line (setting Surcharge As Line Item), and every line is marked as a donation or a fee. The default template adds recurring plan, consent, benefit, tribute, refund date, donor comment and covered-fee details. Supporters link to an existing iPaaS.com Customer with the same email, keeping that Customer's number, company and comment. A Donation Poll Days value that is negative or not a number now stops the first poll with a clear error. The payment method translation covers every payment method Fundraise Up publishes. More coded errors, for subscription settings, unsupported data types and linking to existing iPaaS.com Transactions and Customers, with a clear error when more than one matches. A refused API key or too many requests at once now show their own coded errors instead of a generic connection message, and a Livemode that doesn't match the API key's mode now stops each donation with a clear error instead of transferring nothing. To add these to a subscription created before this update, see the Fundraise Up Version 1.0.3 Upgrade Guide. |
1.0.2 | Coded, searchable error messages: each error the integration records carries a stable code with its cause and resolution. |
1.0.1 | Donation designation (transaction line) capture, with correlation across a donation split into multiple designations, and reliable population of every mapped donation and supporter field. |
1.0.0 | Initial release: capture of Fundraise Up supporters and donations into iPaaS.com. |
Features by Release
The capabilities below are grouped by the version in which they became available, newest first. For the current behavior and any limitations of a given feature, see the linked reference articles and the Fundraise Up Known Limitations article.
Version 1.0.3 — Webhooks, changes after creation, recurring plans and covered fees
Fundraise Up webhook: donations, refunds and recurring plan changes reach iPaaS.com within seconds, with the scheduled poll as a backstop.
Changes after a donation is created: refunds, status changes, edits and recurring plan changes update the donation's existing Transaction.
Recurring plan details: each installment carries its plan's current status, frequency, installment number and dates; the plan's amount, currency and cancellation reason are available to map.
Donor-covered fees: a processing fee the donor covered can arrive as its own fee line, and every line is marked as a donation or a fee.
Donor details: consent, benefit, tribute and donor comment details in the default template.
Matching existing Customers: a supporter links to the iPaaS.com Customer with the same email, keeping that Customer's number, company and comment.
Coded error messages: new codes for subscription settings, for data types the integration doesn't transfer, and for linking to existing iPaaS.com records.
Version 1.0.2 — Coded error messages
Coded error messages: every error the integration can record carries a stable, searchable code with its cause and a resolution you can act on.
Version 1.0.1 — Donation designations
Donation designations: capture a donation's designation lines, with correlation across a single donation split into multiple designations.
Version 1.0.0 — Supporter and donation capture
Supporter capture: donor/supporter records captured into iPaaS.com with their addresses.
Donation capture: donations captured into iPaaS.com with their line items and payment detail.
