Intro to the Salesforce Agentforce Nonprofit Cloud (NPC) integration

Prepare your Salesforce Nonprofit Cloud environment to avoid common setup issues with GoFundMe Pro’s Salesforce Agentforce Nonprofit Cloud (NPC) integration.

Key setup requirements

Complete the following steps before installing the integration to avoid syncing issues.

Turn on Person Accounts

In your Salesforce instance, navigate to Setup > Quick Find, then select Person Accounts. Once turned on, this setting cannot be undone. In older NPSP organizations, turning it on means adopting the Nonprofit Cloud data model.

Activate duplicate and matching rules

Both Account and Person Account objects require duplicate rules to be linked to matching rules. This linkage ensures that duplicates are properly identified and managed across different account types.

Set up a default gift designation

At least one gift designation must be marked as default or transactions won’t sync.

Assign default record types

In your Salesforce instance, select your user profile > Object Settings, and then select Account. Choose a default Person Account record type.

Set up your integration user permissions

Your connected integration user needs the right permissions to sync data successfully.

Required permissions:

• Salesforce permission set: Fundraising Access

Recommended permissions to ensure full access:

• Classy API Access
• GFM Pro Connector All Objects and Fields
• GFM Pro Connector for Salesforce Apex Class Access
• GFM Pro for Salesforce Fundraising All Objects and Fields
• GFM Pro for Salesforce Fundraising Apex Class Access

Understand environment setup and switching

You can only connect one integration to each Salesforce environment. You can’t use both NPSP and NPC integrations in the same environment, but you can use them in different ones, like sandbox and production. If you try to connect both to the same place, you’ll get errors due to conflicting data models. For more information, check out our guide on switching NPC instances or users.

If you switch environments

• Confirm you selected the correct environment (sandbox v. production)
• Make sure you’re logged into the correct Salesforce instance
• If data still syncs to the wrong environment, contact the Care team to clear the cached connection

Historical sync

The integration must create all campaigns, designations, and gift commitments (including the first gift transaction of the plan). If you need past data synced, submit a historical sync request.

Learn how objects map between systems

The table below explains how GoFundMe Pro objects sync with Salesforce NPSP or NPC objects.

Syncing to existing campaigns and designations

The integration creates new records in Salesforce. It doesn’t sync to existing ones. You can remap campaigns or gift designations after creation:

1. Let the integration create the record in Salesforce
2. Remove the GoFundMe Pro ID from the created record
3. Copy the GoFundMe Pro ID to your existing record:
   • Campaign: stay_classy__event_id__c
   • Designation: stay_classy__program_designation_id__c
4. Delete the record that the integration created
5. Keep a record of your mappings
6. Trigger an update:
   • Large bulk updates: Contact the Care team
   • Small update: Edit the record in GoFundMe Pro, then select Save without making any changes

Custom mapping

Custom mapping works differently in the Salesforce Agentforce Nonprofit Cloud (NPC) integration than it does in our NPSP integration. There is no control panel for mapping, so you’ll need to create a Salesforce Flow and use the field mapping utility.

Follow our guide for more information.

Answerable entities

In Nonprofit Cloud, custom questions and answers sync to the same object: GFM Pro Answerable Entity. A Type field defines whether it’s a question or an answer.

What to expect

• Question records show question details
• Answer records show response details and link back to the question

Fundraising pages and teams

Fundraising pages and teams sync as GFM Pro Related Entities in Nonprofit Cloud. They don’t sync as campaigns (unlike NPSP).

Person lookups

• Person Account lookups only populate if the person exists during initial sync
• If the person is created later, the lookup won’t auto-update
  • Edit and save the record in Salesforce to re-trigger matching

Gift Commitments and recurring giving

Recurring giving uses a new structure in Nonprofit Cloud to keep your recurring data organized and predictable.

Key terms

• Recurring plan = Gift Commitment
• Transaction = Gift Transaction
• Schedule = Gift Commitment Schedule

How it works

• Salesforce will create the next scheduled transaction with a status of Unpaid
• When a payment syncs, the integration changes the status of the scheduled record to Paid
• If there is no next Gift Transaction with a status of Unpaid, the integration creates a new Gift Transaction record

Gift Commitment Schedules

Gift Commitment Schedules play a key role in determining whether a transaction can successfully sync to a Gift Commitment record. Here are some important fields to understand:

• Type
  • Create Transactions: Allows transactions to sync
  • Pause Transactions: Prevents transactions from syncing
• Date ranges: The transaction date must fall within the defined date range of the active Gift Commitment Schedule
• Plan status: When the plan is paused in GoFundMe Pro, the status is changed to Paused and transactions will not sync
• Current Gift Commitment Schedule: This field on the Gift Commitment must be populated with the correct schedule that includes the appropriate date range

Next steps

• Install the integration
• Understand all objects and fields
• Find answers to common questions