Skip to main content

Fundraise Up to iPaaS.com Supporter Mapping Documentation

How Fundraise Up Supporter (donor) records are transferred to iPaaS.com as Customer records, with the supporter's address, with the donor's first donation or by Manual Sync.

Summary

Fundraise Up Supporter (donor) records are transferred to iPaaS.com as Customer records (Add or Update), with the supporter's address as a Customer Address. A Supporter is sent with the donor's first donation, before that donation's Transaction, and on a Manual Sync of the supporter. Later donations link to the same Customer and do not send the Supporter again.

ID Format

Manual Sync ID Format

Enter the Fundraise Up Supporter ID, the system record ID of the supporter (example: SPASKKJJ). The integration reads the supporter's current profile, with the address, from Fundraise Up and sends it to iPaaS.com.

External ID Format (saved after sync)

After a successful transfer, iPaaS.com saves the Fundraise Up Supporter ID as the external ID of the iPaaS.com Customer, on a dedicated external-ID record. That link is how later transfers of the same supporter find and update the same Customer. Fundraise Up addresses have no ID of their own, so the child Customer Address is linked through the supporter.

The default template also writes the Supporter ID into a new Customer's CustomerNumber. See Duplicate or Conflicting Mappings for how an existing Customer is matched by email.

Deleted Record Support

Inbound Delete is not supported. Fundraise Up is the system of record for supporters, and the integration only sends data to iPaaS.com, so a supporter deleted in Fundraise Up is not deleted in iPaaS.com.

Custom Field Support

Fundraise Up custom fields belong to donations, not to supporters, so this collection has no Fundraise Up custom fields to map. Donation custom fields are written to the Transaction: see the Fundraise Up to iPaaS.com Donation Mapping Documentation for how to configure them.

Mapping Collection Status

  • Status: Enabled

  • Trigger Events: Donation prerequisite (automatic) or Manual Sync.

Trigger

Behavior

Donation prerequisite

When a donation's supporter is not yet linked to an iPaaS.com Customer (in practice, with the donor's first donation), the Donation transfer sends the Supporter first, so the Customer exists before the Transaction is written. Later donations link to the existing Customer and do not send the Supporter again. You don't configure this: it is part of every Donation transfer, whether the donation arrived by webhook, poll or Manual Sync.

Manual Sync

Transfer a single Supporter from the iPaaS.com Manual Sync page at any time, using the Fundraise Up Supporter ID. It sends the supporter's current profile again and updates the linked Customer. Use it for a donor whose profile changed in Fundraise Up.

There is no scheduled Supporter sync. Fundraise Up's Supporter webhook events are accepted and run nothing, so a change to a donor's profile in Fundraise Up reaches iPaaS.com only through a Manual Sync of the supporter, or an update you make to the iPaaS.com Customer directly.

Duplicate or Conflicting Mappings

This mapping transfers Supporters from Fundraise Up to iPaaS.com. Fundraise Up is the system of record for donor identity, and the integration sends data to iPaaS.com only: there is no mapping collection that writes Supporters back to Fundraise Up.

Collision Handling

This collection and its child collection have no Collision Handling Method setting. Duplicates are prevented in these ways instead:

  • External ID link. Once a supporter is transferred, its saved external ID routes every later transfer to the same Customer.

  • Automatic matching by email. When a supporter has no saved link, the integration looks for an iPaaS.com Customer with the supporter's email and links it, rather than create a second Customer. iPaaS.com keeps Customer emails unique within a company, so there is at most one match. This also applies to a Customer that another system created.

  • What a matched Customer keeps. A Customer created by another system keeps its CustomerNumber, Company and Comment (the template's keep-formulas) and its own addresses. The integration adds one address of its own and writes the mapped fields, so the Customer's first and last name become the supporter's.

Kept on update

iPaaS.com replaces the whole Customer on an update. So the template keeps what Fundraise Up doesn't own: CustomerNumber keeps an existing Customer's number (a new Customer gets the Supporter ID), and Company and Comment keep their existing values.

Unmapped Field Overwrite Risk

Warning: The iPaaS.com API also replaces the whole Customer Address on an update. The following Customer Address fields are not mapped in the default template mappings for Add/Update Fundraise Up Supporter Address TO iPaaS.com. Any existing values in these fields on the address the integration writes will be overwritten with empty values each time the address is sent, unless you add mappings to keep them:

  • FirstName (on the address itself, distinct from the Customer's FirstName)

  • LastName (on the address)

  • Company (on the address)

  • Address3

  • IsPrimaryBilling

  • IsPrimaryShipping

  • Type (the Customer Address type)

To keep one of these, add a Dynamic Formula mapping that returns the existing value on an update, for example return DestinationValue != null ? DestinationValue.IsPrimaryBilling : false; mapped to IsPrimaryBilling. The Company and Comment mappings on the Supporter collection use the same pattern.

Supported Child Collections

  • Add/Update Fundraise Up Supporter Address TO iPaaS.com (Child of Supporter): Transfers the supporter's address as an iPaaS.com Customer Address. Fundraise Up keeps one address per supporter, so each Supporter transfer writes at most one Customer Address. It always runs with its parent Supporter transfer, never on its own.

System Caveats

Fundraise Up Caveats

  • Supporter changes are not read. The integration does not read supporter changes from Fundraise Up, and later donations do not send the Supporter again. Profile changes reach iPaaS.com only through a Manual Sync of the supporter.

  • The current profile is sent. A Supporter transfer reads the supporter's current profile from Fundraise Up, not the copy of the donor details on the donation.

  • Anonymous donations have no supporter. When a donor gives anonymously, the donation has no supporter, so no Supporter is sent; the Transaction gets the email email@email.com from the Donation EmailAddress mapping. See the Fundraise Up to iPaaS.com Donation Mapping Documentation.

  • One address per supporter. Sending a Supporter again with a changed address updates the same Customer Address.

  • Missing or partial addresses. When Fundraise Up has no address for a supporter, no Customer Address is written and no error is raised. When it has one, a Customer Address is written from it, even if some of its fields are blank.

  • Phone numbers are carried as entered. Fundraise Up doesn't validate phone numbers, so a number that isn't valid reaches iPaaS.com as the donor typed it. A downstream system that refuses an invalid phone (for example Raiser's Edge NXT) won't take that donor's gift until the Customer's phone is fixed. See Fundraise Up Known Limitations.

  • Country codes arrive lowercase. Fundraise Up sends the country as a lowercase two-letter ISO 3166-1 code (us, ca, gb). If a downstream system expects uppercase codes or country names, convert the value with a Lookup Translation on the Country mapping. See Fundraise Up Known Limitations.

iPaaS.com Caveats

  • Required API fields. iPaaS.com requires CustomerNumber and EmailAddress on every Customer. A new Customer gets the Supporter ID as its number; an existing Customer keeps its own. A supporter without an email can't be written as a Customer.

  • Unique emails. iPaaS.com keeps Customer emails unique within a company, so two supporters with the same email update the same Customer.

  • Customers shared with other integrations. When another integration (a CRM, an accounting system, another donation platform) also writes the same Customer, the most recent write wins on any field both map. The template keeps an existing Customer's CustomerNumber, so this integration does not re-key a Customer another system created.

Setup Requirements

For full setup steps see the Installation Instructions and Connections and Settings. The integration-wide setup (the Fundraise Up API key, with Read permission on Donations, Supporters, Recurring plans and Events in the mode Livemode selects) is documented there and not repeated here.

If Livemode doesn't match the mode your API key was made in, donations don't transfer, so their Supporters aren't sent either: each donation stops with FUUP-VALD-1006, which names the Livemode value to set. Make sure Livemode matches the key's mode before the first transfer.

Integration Flow

A Supporter transfer runs before a donation's Transaction when the donor is not yet linked to a Customer, and on a Manual Sync of the supporter. The processing order is:

  1. Trigger. Either a Donation transfer finds that its donor is not yet linked to an iPaaS.com Customer, or a Manual Sync is started with a Supporter ID.

  2. Read the supporter. The integration reads the supporter's current profile, with the address, from Fundraise Up.

  3. Find the existing Customer. If the supporter is linked, the transfer is an Update of the linked Customer. If not, the integration looks for a Customer with the supporter's email and links it; otherwise the transfer is an Add. Delete is not supported.

  4. Map the Supporter fields. Each mapping in this collection builds the iPaaS.com Customer.

  5. Map the address. The supporter's address goes through the Add/Update Fundraise Up Supporter Address TO iPaaS.com child collection. If the donor gave no address, no Customer Address is written and no error is raised.

  6. Send to iPaaS.com. The Customer, with its address, is sent to iPaaS.com as an Add or an Update. If the Supporter was sent for a donation, the Donation transfer then continues with the linked Customer.

Mappings

Add/Update Fundraise Up Supporter TO iPaaS.com

iPaaS.com data type: Customer

Description: Transfers Fundraise Up supporters (donors) to iPaaS.com as Customers, with the donor's first donation or by Manual Sync. Maps the email, first name and last name, and keeps an existing Customer's number, Company and Comment.

Mapping Filter: None. Every supporter sent with a donation or by Manual Sync is processed.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Dynamic Formula

return DestinationValue != null ? DestinationValue.CustomerNumber : Id;

CustomerNumber

Required. A new Customer gets the Fundraise Up Supporter ID. An existing Customer keeps the number it already has, so a Customer another system created, and matched by email, is not re-keyed. iPaaS.com requires a CustomerNumber on every Customer.

Field

Email

EmailAddress

Required. The supporter's email. iPaaS.com requires it on every Customer and keeps it unique within the company; the integration matches an existing Customer by it.

Field

FirstName

FirstName

Recommended. The supporter's first name, so downstream systems can address the donor by name.

Field

LastName

LastName

Recommended. The supporter's last name.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Company : null;

Company

Recommended. Keep this mapping: it keeps the Company an existing Customer already has. Fundraise Up doesn't send a company, and an update replaces the whole Customer.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Comment : null;

Comment

Recommended. Keep this mapping: it keeps the Comment an existing Customer already has. Fundraise Up doesn't send a comment, and an update replaces the whole Customer.

Add/Update Fundraise Up Supporter Address TO iPaaS.com (Child)

iPaaS.com data type: Customer Address

Description: Transfers the supporter's address to iPaaS.com as a Customer Address. It runs only with its parent Supporter transfer. Fundraise Up keeps one address per supporter.

Mapping Filter: None. The address of every transferred supporter is processed.

Field Mapping Table

Mapping Type

Source Field (Fundraise Up)

Destination Field (iPaaS.com)

Description

Field

Line1

Address1

Recommended. The first address line. Empty when the donor gave no postal address.

Field

Line2

Address2

Optional. The second address line. Often empty.

Field

City

City

Recommended. The city.

Field

Region

Region

Recommended. The state, province or region, as Fundraise Up sends it (for example GA for a US state).

Field

PostalCode

PostalCode

Recommended. The postal or ZIP code.

Field

Country

Country

Recommended. The country, as a lowercase two-letter ISO 3166-1 code (us, ca, gb). Convert it with a Lookup Translation if a downstream system expects another form.

Field

Phone

PhoneNumber

Optional. The supporter's phone number, as the donor entered it. Fundraise Up keeps one phone per supporter, so it is written to the address. Empty when the donor gave none.

Error Handling

Errors from this mapping collection appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs. An error from a Fundraise Up call includes Fundraise Up's Request-Id: quote it when you contact your MiSP or iPaaS.com support about that error.

For the full catalog of error messages, descriptions, and resolution steps, see Fundraise Up Error Messages.

Testing & Validation

Test Scenarios

  1. Make a donation in Fundraise Up with a donor email that no iPaaS.com Customer has. After the donation arrives, check that a new Customer exists with the Supporter ID as CustomerNumber, and the correct EmailAddress, FirstName and LastName, plus a Customer Address if the donor gave one.

  2. Make a second donation from the same donor. Check that no second Customer is created and the second Transaction links to the same Customer.

  3. Make a donation from a donor with no postal address. Check that the Customer is written and no Customer Address is created, with no error.

  4. Create a Customer in iPaaS.com with a donor's email, a Customer Number, a Company and a Comment, then make that donor's first donation. Check that the donation links to that Customer, which keeps its Customer Number, Company and Comment.

  5. Change a donor's name in Fundraise Up, then Manual Sync that supporter by its Supporter ID. Check that the linked Customer shows the new name and keeps its Company and Comment.

  6. Change a donor's street address in Fundraise Up, then Manual Sync that supporter. Check that the Customer's address shows the new street address and no second address was added.

  7. Make a donation from a donor outside the US (for example in the UK) and check that the Customer Address's Country is the lowercase code (gb).

Validation Checklist

  • The Fundraise Up API key in the subscription settings is active and has Read permission on Donations, Supporters, Recurring plans and Events in the mode the Livemode setting selects, and Livemode matches the mode the key was made in.

  • If another integration also writes Customers, it is agreed which integration owns CustomerNumber and the other shared fields.

  • Downstream systems that read the Customer Address have a plan for lowercase country codes (a Lookup Translation, a conversion at the destination, or accepting lowercase).

  • The unmapped Customer Address fields listed under Unmapped Field Overwrite Risk have been reviewed, and any you need to keep have a DestinationValue keep-mapping.

Additional Notes

Operational Notes

  • API unavailability. If Fundraise Up is unavailable when a Supporter transfer runs (for a donation or by Manual Sync), the transfer fails and the error appears in Dashboard / Integration Monitoring / Error Logs. A later poll does not read the donation again. Once Fundraise Up answers, re-send the donation from the error log, or Manual Sync the donation or the supporter.

  • Profile changes need a Manual Sync. A supporter whose profile changes in Fundraise Up is not sent again automatically, not even with a new donation. Use a Manual Sync of the supporter, or update the iPaaS.com Customer directly.

  • Existing subscriptions. Template changes are not applied to subscriptions created on an earlier version: the CustomerNumber, Company and Comment keep-formulas are added by hand. The steps are in the Fundraise Up Version 1.0.3 Upgrade Guide.

Related Documents

Related Mapping Documentation

Did this answer your question?