Bring your online giving data into the systems that power your mission.
The Fundraise Up integration with iPaaS.com automatically syncs donation data from your Fundraise Up account into iPaaS.com on a scheduled basis. Each donation brings with it the associated donor (supporter) record, including contact details, address and the payment record. This data flows into iPaaS.com where it can be routed to connected CRM, ERP, fund accounting, and other nonprofit systems, giving your team a unified view of donor activity without manual exports or imports.
Fundraise Up subscribers often integrate the doner management software with Raiser’s Edge NXT, Salesforce, NetSuite, and Microsoft Dynamics 365 Business Central, enabling donation and donor data to flow directly into the systems your team works in every day.
No. This integration is source-only, data flows from Fundraise Up into iPaaS.com. The Fundraise Up REST API does not expose write endpoints for donations or supporters, so records cannot be created or updated in Fundraise Up from iPaaS.com.
New donations are discovered through scheduled polling rather than real-time webhooks. The time between a donation being made in Fundraise Up and its appearance in iPaaS.com is equal to the configured poll interval for the subscription.
Yes. When polling is first enabled, an initial backfill step paginates the full Fundraise Up donation history up to the configured lookback period. This prevents the first scheduled poll from re-importing all historical donations.
How does the integration handle duplicate donor records? Collision handling is configurable. When an incoming supporter matches an existing iPaaS.com Customer, email address, you can configure the integration to remap and link (recommended), update and link, update without linking, or error. Remap and Link is recommended to avoid duplicate Customer records.
Yes. Fundraise Up exposes custom fields on donation records. These can be mapped to iPaaS.com Custom Fields on the Transaction record and routed to connected downstream systems. The payment record also carries the processor transaction reference (e.g. Stripe charge ID) as a custom field for reconciliation purposes.
Refunded donations are picked up by the next scheduled poll. Subscribers who need to track refunds as distinct accounting events can configure a mapping filter to route refunded donations through a separate Mapping Collection in iPaaS.com.
Yes. Recurring donation frequency information (‘Monthly’, ‘Every 4 Weeks’, etc.) is included on the donation record and can be mapped to connected systems.
Yes. Fundraise Up issues separate API keys for live and test environments. Setting Livemode to false in the iPaaS.com subscription settings and using a test API key allows the integration to run against Fundraise Up's sandbox data before processing live donations.

Donations: Transactions, including amount, status, campaign, recurring plan frequency, and custom fields
Supporters (Donors):
Donor contact records including name, email address, and phone number
Supporter Addresses:
Donor address records synced as child customer address
Payments:
Transaction payment records, including payment method, and payment identifier








Discover how iPaaS.com can simplify even the most complex integrations.
© 2026 iPaaS.com | Privacy Policy | Terms of Use | Legal | Status