Connecting Your Salesforce NPC Org

Last updated: June 11, 2026

Connecting Your Salesforce NPC Org

Before You Start

Make sure your Salesforce org meets these prerequisites:

  • Nonprofit Cloud is enabled and configured

  • Person Accounts are enabled (required for NPC individual supporters)

  • You have a dedicated integration user with:

    • Fundraising Access permission set license

    • Fundraising User permission set If you're unsure about any of these, check with your Salesforce consultant before proceeding.

Step 1: Request NPC Integration Access

Contact your WeGive CS representative to enable the NPC integration on your account. This is a separate integration from NPSP, so your CS contact will coordinate the switch with you.

Step 2: Create an External Client App in Salesforce

Before connecting WeGive, you need to create an External Client App (ECA) in your Salesforce org. Salesforce replaced Connected Apps with ECAs starting in Spring '26.

Create the ECA

  1. Log into Salesforce and go to Setup

  2. In the Quick Find box, search for External Client App and select it

  3. Click New External Client App

  4. Fill in the following:

    • Name: WeGive

    • Enable OAuth Settings: Checked

    • Callback URL: https://api.wegive.com/api/oauth/npc/callback

Set OAuth Scopes

Add the following OAuth scopes:

  • Manage user data via APIs (api)

  • Perform requests at any time (refresh_token, offline_access)

Configure Flow and Security Settings

Under Flow Enablement:

  • Enable Authorization Code and Credentials Flow: Yes

  • All other flows: No

Under Security:

  • Require Secret for Web Server Flow: Yes

  • Require Secret for Refresh Token Flow: Yes

Click Save.

Edit ECA Policies

  1. From the ECA detail page, click Manage or Edit Policies

  2. Set IP Relaxation to Relax IP restrictions

  3. Save

Copy Your Credentials

On the ECA Settings page, scroll down to OAuth Setting and expand the section and click on the Consumer Key and Consumer Secret. You will need these when connecting WeGive.

Add Remote Site

  1. In Salesforce Setup, go to Security > Remote Site Settings

  2. Click New Remote Site

  3. Enter:

    • Remote Site Name: wegive_api

    • Remote Site URL: https://api.wegive.com

  4. Save

Note: The ECA may take up to 10 minutes to become active after creation. If you see an authorization error when connecting WeGive, wait a few minutes and try again.

Step 3: Connect WeGive to Salesforce

  1. In the WeGive dashboard, go to Settings > Integrations

  2. Select Salesforce Nonprofit Cloud Setup

  3. On the Connection tab, toggle Enable Integration on

  4. In the Salesforce Login URL field, enter your Salesforce My Domain URL (e.g. https://yourorg.my.salesforce.com/)

  5. Enter the Consumer Key and Consumer Secret from the ECA you created in Step 2. To find these in Salesforce, go to Setup > External Client App, open the WeGive ECA, and copy the credentials from the detail page.

  6. Click Save, then click Test Connection to verify connectivity

  7. You will be redirected to Salesforce to approve the OAuth connection. Log in with your integration user credentials and authorize access.

Once connected, the page will show OAuth connected and a last synced timestamp. You can use the Sync button to trigger a manual sync at any time.

Step 4: Configure Your Settings

After connecting, you'll see the NPC integration settings panel. Here you can:

  • Enable/disable sync toggles for each data type (supporters, transactions, recurring, campaigns, etc.)

  • Map your WeGive funds to Salesforce GiftDesignation records

  • Verify your Person Account setup is detected correctly

  • Review default field mappings and add custom field mappings if needed

See the Push Configuration and Pull Configuration articles for details on each toggle.

Salesforce Licensing Notes

The NPC objects (GiftTransaction, GiftCommitment, GiftDesignation, etc.) require the Fundraising Access permission set license. This is what grants access to create and modify records on these objects.

We recommend creating a dedicated integration user rather than using a personal admin account. Your Salesforce consultant can advise on the best approach for your org's license allocation.