​
Setup Requirements

Before you can use the WeGive Salesforce integration, you need to ensure your Salesforce instance meets the following requirements.

​
Required Salesforce Editions

The integration requires one of the following Salesforce editions:

  • Enterprise Edition
  • Unlimited Edition
  • Developer Edition

​
Required Salesforce Packages

​
WeGive Managed Package

The WeGive managed package provides all the custom objects and fields needed for the integration. You must install this package before setting up the integration.

​
Package Contents

The managed package includes the following custom objects:

  • wegive__Pledge__c - For managing pledges
  • wegive__Payout__c - For tracking payout summaries
  • wegive__Communication_List__c - For managing communication lists
  • wegive__Communication_Preference__c - For tracking communication preferences
  • wegive__Event__c - For campaign events
  • wegive__Event_Ticket__c - For event tickets
  • wegive__Event_Registration__c - For event registrations
  • wegive__Fundraiser__c - For campaign fundraisers

​
Nonprofit Success Pack (NPSP)

The integration is designed to work with the Nonprofit Success Pack (NPSP). You must have NPSP installed in your Salesforce instance. The integration uses several NPSP objects and features:

  • npe01__OppPayment__c - For payment tracking
  • npe03__Recurring_Donation__c - For recurring donations
  • npsp__Allocation__c - For fund allocations
  • npsp__General_Accounting_Unit__c - For funds
  • npsp__Partial_Soft_Credit__c - For individual soft credits
  • npsp__Account_Soft_Credit__c - For organization soft credits

​
Required User Permissions

The Salesforce user account used for the integration must have the following permissions:

  • API Enabled
  • Modify All Data
  • Customize Application
  • View Setup and Configuration
  • View All Data

​
Required API Access

  • API access must be enabled for your Salesforce instance
  • The integration uses the Salesforce REST API
  • For Salesforce instances created after Summer 2023, the OAuth username-password flow must be explicitly enabled

​
Field-Level Security

All fields involved in the integration must be visible to the API in Salesforce, even for system administrators. This includes:

  • Standard fields on Contact, Account, Opportunity, and Campaign objects
  • Custom fields from the WeGive managed package
  • Custom fields from NPSP
  • Any custom fields you’ve mapped in the integration

​
Environment Considerations

  • The connection will only be successful if both the WeGive and Salesforce instances are the same type (production or sandbox)
  • Ensure your Salesforce instance has sufficient API call limits for your expected usage
  • Consider enabling debug logs for the integration user during initial setup

​
Next Steps

After meeting these requirements, you can proceed to:

  1. Configure the integration in WeGive
  2. Set up field mappings
  3. Test the integration in a sandbox environment
  4. Deploy to production

For detailed configuration instructions, see the Configuration Options page.