Salesforce Integrations require a bit of configuration in Salesforce before you can input details into WeGive.
Salesforce has 3 Integration requirements before you can fully integrate into WeGive:
If you are in your WeGive sandbox, create a Salesforce sandbox that is a duplicate of your Salesforce production environment.
Designate or create an admin account in Salesforce with marketing permissions and note its credentials.
Create a connected app in Salesforce with full access permissions, making sure to enable OAuth.
When you are testing your integration, use your Salesforce Sandbox environment. When you are ready to go live, use your Salesforce Production environment. Click here for more instructions on accessing your Salesforce Sandbox environment.
Integration Instructions:
Login to your organization's Salesforce account to complete the following instructions for integration.
Click to Setup in the top right corner of your screen.
Type App Manager in the navigation search bar.
Fill out the corresponding fields under New Connected Apps:
Connected App Name: WeGive
API Name: WeGive
Contact Email: [email protected]
Enable OAuth Settings: Check On
Callback URL:
When creating your Production Environment use: https://super.givelist.app
When creating your Sandbox Environment use: https://api.sandbox.wegive.com
Selected OAuth Scopes: Highlight and move all selected OAuth scopes to the Available OAuth Scopes using the arrows.
Require Secret for Web Server Flow: Check On
Require Secret for Refresh Token Flow: Check On
Once you have connected your WeGive app in Salesforce, you will be able to manage it from your Lightning Experience App Manager by clicking into the WeGive tab. Click View.
Once you have clicked into WeGive, scroll to the API (Enable OAuth Settings) section and click on Consumer Key and Secret: Manage Consumer Details. Copy and paste the Consumer Key (Client ID) and Secret Key (Client Secret) into WeGive.
Return back to the Lightning Experience App Manager by clicking into the WeGive tab. This time, click "Manage" instead of "View."
From your Salesforce Home Screen, click on Security and then click on Remote Site Settings.
Click New Remote Site
Under Remote Site Edit, add this information:
Remote Site Name: wegive_api
Remote Site URL:
If using Sandbox environment: https://api.sandbox.wegive.com
If using Production environment https://super.givelist.app
Once you have your Consumer and Secret key, toggle back over to your WeGive Integration page found in the left side bar. Make sure you have Added the Salesforce Integration.
If your Salesforce sandbox was created during or after Summer 2023, enable Username-Password Flow in OAuth and Open ID Connect Settings.
Click into your Salesforce Integration General Settings:
Copy and paste the Consumer and Secret key from Salesforce into the WeGive Client Id (Consumer Key) and Client Secret (Secret Key) fields.
Enter your Salesforce Username and Password.
Your Instance URL is:
Sandbox: https://test.salesforce.com/
Production: https://login.salesforce.com/
You have the ability to specify your sync settings.
You can click over to Logs to see a full display of all the integrations that have happened.
After you have completed the previous steps, you can click Test Connection. If the test succeeds, you can click Sync Salesforce to enable your integration.
Mapping Rules:
Here is a list of which WeGive fields populate in Salesforce and vice versa:
A New Donor in WeGive creates a New Contact and New Account in Salesforce if that donor does not yet exist in Salesforce. If the Donor does exist in Salesforce, WeGive syncs the information of that Salesforce Donor with the corresponding WeGive Donor.
Campaigns in WeGive sync with Campaigns in Salesforce.
Donations in WeGive sync with Opportunities in Salesforce.
Donations in WeGive that are attached to a Campaign or a Recurring Plan attach to the respective Salesforce Campaign or Recurring Donation.
Recurring Plans in WeGive sync with Recurring Donations in Salesforce.
Designations in WeGive sync with GAU (General Accounting Units) in Salesforce.
There is a one minute buffer period for changes in WeGive to sync to Salesforce and vice versa.
WeGive does multiple checks to ensure duplicates are not created in Salesforce, even if WeGive does not have an existing link defined between the WeGive and the Salesforce Donor. WeGive will only create a new donor after searching for that donor with multiple checks.
You can change the mapping of any WeGive field to any Salesforce field and vice versa or disable the mapping.