Pull Configuration & Sync Settings
Last updated: April 29, 2026
Pull syncs run on a scheduled cycle, pulling changes made directly in Salesforce back into WeGive. The default pull frequency is every 15 minutes, but this is configurable. All pull and sync settings are on the Sync Configuration tab.
Entity Toggles
Pull toggles available on the Sync Configuration tab:
Toggle | What It Pulls |
Pull donors | Person Account records (individual supporters) |
Pull households | Household Account records |
Pull companies | Organization Account records |
Pull campaigns | Campaign records |
Pull funds | GiftDesignation records |
Pull recurring donations | GiftCommitment records |
Pull transactions | GiftTransaction records |
Pull soft credits | GiftSoftCredit records |
Pull campaign donors | CampaignMember records |
Pull pledges | Pledge GiftCommitment records |
Pull refunds | Refund records |
Pull merge accounts | Account merges performed in Salesforce |
Pull Donors
Pulls Person Account records from Salesforce into WeGive as individual supporters. This detects new Person Accounts, updates to existing records (name, email, address, phone), and account merges performed in Salesforce.
Pull Companies
Pulls Account records with Organization record types from Salesforce into WeGive as organization supporters.
Note: The push side uses a single "Push donors" toggle for both individuals and organizations, but the pull side separates them into "Pull donors" (Person Accounts) and "Pull companies" (Org Accounts). We're aware this is inconsistent and have it tracked for a future update.
Pull Households
Pulls Household Account records from Salesforce into WeGive. If your org does not use Household Accounts, leave this off.
Pull Campaigns, Pull Funds, Pull Recurring Donations, Pull Transactions
These toggles pull the corresponding Salesforce records into WeGive. This is useful when your team creates or updates records directly in Salesforce and you want those changes reflected in WeGive.
Pull Soft Credits, Pull Campaign Donors, Pull Pledges, Pull Refunds
These pull their respective record types from Salesforce into WeGive.
Pull Merge Accounts
Detects account merges performed on the Salesforce side and updates WeGive's internal record references so the link between systems stays correct.
Contact Sync Options
Sync contacts with emails only - When enabled, only Salesforce contacts that have at least one email address will be imported into WeGive. This helps avoid importing incomplete records.
Sync Schedule
Two configurable fields:
Setting | Description |
Pull frequency (minutes) | How often Salesforce data is pulled during the scheduled sync. Default is 15. |
API version | The Salesforce API version used for NPC calls. Default is 59.0. |
Transaction Status Names
These fields control how WeGive transaction statuses are mapped to Salesforce GiftTransaction status values when pushing records:
Setting | Default Value |
Success status | Paid |
Failed status | Failed |
Pending status | Pending |
If your Salesforce org uses different status values (for example, custom picklist values), you can update these fields to match.
Payment Method Labels
These fields control how WeGive payment method types are labeled when pushed to Salesforce:
Setting | Default Value |
Card payment method | Credit Card |
Bank payment method | ACH |
Record Type Configuration
These fields store the Salesforce Record Type IDs that the integration uses to create and identify records:
Setting | Description |
Person Account record type ID | The Salesforce record type ID for individual donors (Person Accounts). |
Organization record type ID | The Salesforce record type ID for organization/company donors. |
Household record type ID | The Salesforce record type ID for household accounts. Leave empty to disable household sync. |
To find your Record Type IDs in Salesforce, go to Setup > Object Manager > Account > Record Types and copy the ID from the URL of each record type.
Login Contact Roles
This section shows the AccountContactRole roles that will receive logins on Organization Accounts during sync. These are auto-populated when you connect via OAuth.
Known issue: This feature currently queries AccountContactRole, which is a legacy Salesforce object. NPC uses AccountContactRelation instead. As a result, Login Contact Roles does not work on NPC orgs. Do not rely on this feature until it is resolved.
Pull Gift Types
Controls which GiftType values to pull from GiftTransaction records. Remove a type to exclude it from sync. These are auto-populated on OAuth connect.
Default values: Individual, Organizational
Pull Payment Methods
Controls which PaymentMethod values to pull from GiftTransaction records. Remove a method to exclude it from sync. Auto-populated on OAuth connect.
Default values: Unknown, Check, Credit Card, ACH, Cash, In-Kind, Stock, Asset, Cryptocurrency, PayPal, Venmo
Pull Transaction Statuses
Controls which Status values to pull from GiftTransaction records. Remove a status to exclude it from sync. Auto-populated on OAuth connect.
Default values: Unpaid, Paid, Failed, Fully Refunded, Written-Off, Cancelled, Pending
Pull Commitment Statuses
Controls which Status values to pull from GiftCommitment records (recurring donations and pledges). Remove a status to exclude it from sync. Auto-populated on OAuth connect.
Default values: Active, Closed, Lapsed, Failing, Paused, Draft
Hidden Record Types
Add Account Record Type IDs to exclude from sync. This is for record types like Vendor, Partner, or other account types that should not be imported as supporters. Enter the Record Type ID and click Add.
Recurring Donation Sync
Sync all recurring donations - When enabled, all recurring donations are pulled regardless of status (subject to the commitment status filter above). When disabled, only Active recurring donations are pulled.
Manual Sync
You can trigger a manual sync from the Connection tab by clicking the Sync button. This syncs all enabled entity types.
Integration Logs
Every sync operation, successful or failed, is recorded in Integration Logs (accessible from the left sidebar under Settings > Integrations). Each log entry shows what was pushed or pulled, whether it succeeded or failed, and the specific error message from Salesforce if applicable.
Integration Locks
Integration Locks prevent duplicate sync operations from running at the same time. This protects data integrity during high-volume sync periods. If a sync appears stuck, contact your WeGive CS representative to have a lock manually released.