Connect Fundraise Up to thousands of other apps and services using native API integrations and third-party connectors.
Fundraise Up includes built-in integrations that enable you to natively connect Fundraise Up to your organization’s CRM and marketing tools in real time.
Integrations are enabled and managed from the settings area in the Fundraise Up Dashboard.
Most integrations include controls for determining what types of records are synced to connected apps, and how the records are formatted and deduplicated.
Syncing test mode transactions
When using test mode to experiment with platform settings, you can opt to send test transactions to connected apps. This enables you to configure and refine mapping rules so that values from Fundraise Up are synced to the expected properties in your app. By default, the Sync test data option is disabled when you enable an integration, but it can be enabled form the integration’s settings.
When the Subaccounts feature is enabled, you can opt to sync data from a primary account’s subaccounts to apps connected at the primary account level. This is useful for tracking donations and simplifying reporting when your organization uses a chapter-based or federated model.
Customizable record names
When supported by a connected app, it is possible to define a custom naming structure for records that Fundraise Up creates. For example, the Salesforce integration enables you to define the format of the account and opportunity records created by Fundraise Up.
When supported by a connected app, Fundraise Up surfaces app-specific settings that help you tailor integrations to your organization’s needs. For example, the HubSpot integration enables you to programmatically set subscription types, and the Salesforce integration allows you to map transaction statuses to opportunity stages.
Explore the guides for each integration to see available settings.
Many Fundraise Up integrations enable you to define the destination objects and properties of data values synced from the platform. Support for mapping rules is based on the flexibility of a connected app’s API.
Mapping rules are configured by linking a Fundraise Up object and property to an object and property in a connected app. A value sent from Fundraise Up will be written to a property in a connected app. In some cases, Fundraise Up will define some rules for you to reduce the implementation steps you need to take. These rules can be removed if needed.
Mapping rules examples:
- Linking the
supporter emailvalue from Fundraise Up to the
Fundraise Up Connected app Object: Donation Object: Contact Property: Supporter email Property: email
- Linking the Campaign
IDvalue from Fundraise Up to the
order numberproperty on the Opportunity object in a connected app.
Fundraise Up Connected app Object: Campaign Object: Opportunity Property: ID Property: order number
In some cases, a Fundraise Up integration can be configured to use special rules. These types of rules use if/then conditions that enable you to link a property’s value in Fundraise Up to a property’s value in a connected app.
Special rule examples:
- If Campaign equals “Shelter” in Fundraise Up, then set the campaign in Salesforce to “Shelter.”
- If Designation equals “Areas of Greatest Need” in Fundraise Up, then set the campaign in Salesforce to “General Donations.”
Fundraise Up’s built-in integrations include settings for managing the sync behavior for records.
By default, the automatic sync option is disabled when you connect an integration to Fundraise Up. This enables you to configure the integration’s settings and mapping rules before synchronizing records.
Once you are satisfied with the configuration for an integration, we recommend enabling the automatic sync feature.
Most built-in integrations include the option to manually sync records from Fundraise Up to connected apps. This option is useful when you elect to not use the automatic sync function, or when you want to resync previous records.
Resyncing previous records
When you make changes to record properties for past donations in Fundraise Up, you can use the manual sync option to update the associated records in a connected app. This is beneficial for scenarios where an incorrect mapping was made in Fundraise Up.
When you manually sync records, you can opt to sync all records or specify date range. Narrowing the sync scope using a date range is useful when you need to target a specific set of records or want to avoid resyncing a significant number of records.
You can disconnect an integration at any time from its settings page. Disconnecting and then reconnecting an integration using the same credentials will preserve the settings and mapping rules set before the app was disconnected form Fundraise Up.
These are the integrations natively supported by Fundraise Up.
Marketing & analytics
These integrations enable you to pass conversion data from Fundraise Up to ads platforms and analytics tools.
These integrations enable you to connect Fundraise Up to thousands of other apps and services using third-party tools.
These integrations enable you to add and automate donation matching functionality.
These native integrations enable you to push data from Fundraise Up to your CRM and use mapping rules to route data to objects and properties.
- Microsoft Dynamics 365
- Neon CRM
- Raiser’s Edge NEXT
Leverage Fundraise Up’s JavasScript API to create custom integrations with your apps.
These integrations power the payment methods you provide to donors at Checkout.
Connection best practices
Most Fundraise Up integrations are connected and authenticated using OAuth. We recommend connecting our platform and your apps using dedicated service user accounts. This way, you can narrow the scope of user permissions to include only what is necessary for the integration, and avoid issues with personal accounts that may be deleted or have their permissions levels changed.
When an integration is connected using an API key, we recommend creating dedicated credentials for use with Fundraise Up. This way, you can narrow the scope of permissions to include only what is necessary for the integration to function.