All configuration lives under Settings > Integrations > Salesforce Nonprofit Cloud in the WeGive dashboard.
Connection settings
Record types
These are Salesforce record type IDs, not names, and they are discovered automatically when you authorize. Record types are stamped on create only. Changing a record type in Salesforce after the record exists is never overwritten by WeGive.
Sync toggles
Every synced object has independent pull and push toggles, and most have a pull-deleted toggle that soft-deletes the WeGive record when the Salesforce record is deleted.
The dashboard still shows Push toggles for Companies and Households, but enabling them does nothing — WeGive has no code path that pushes a company or household record to NPC. New and updated companies/households in WeGive never appear in Salesforce; the reverse direction (Salesforce → WeGive) works normally. This is a known issue.
Sync behavior
Pull filters
Filters scope the pull to a subset of records. Each is seeded with every active picklist value at connect time; remove values to exclude them.
The seeded lists reflect your org’s picklists at connect time, so an org with custom picklist values sees those values too. A record whose value is not in the list is skipped on pull, so if a category of gifts is missing from WeGive, check these filters first. An empty list applies no filter for that field.
Status mapping
WeGive maps NPC statuses to its own transaction and recurring plan statuses. If your org has customized the GiftTransaction.Status or GiftCommitment.Status picklists, override the defaults here.
Cancelled and refunded transactions are not covered by a dashboard setting — WeGive always writes Written-Off for a cancelled transaction and Fully Refunded for a fully-refunded one, hardcoded in the integration. A partially-refunded transaction is kept at whatever the Success status is set to (Paid by default) rather than switching to a separate value, since NPC itself only exposes a boolean partial-refund flag, not a distinct status. If your org’s GiftTransaction.Status picklist doesn’t have Written-Off or Fully Refunded values, the push for that transaction fails — add those exact values to your picklist rather than expecting WeGive to use a substitute.
Payment method labels
Card payment method and Bank payment method set the GiftTransaction.PaymentMethod value WeGive writes for card and bank charges. Defaults are Credit Card and ACH. Change them only if your org’s PaymentMethod picklist uses different values; a value that is not in the picklist is rejected by Salesforce and the push fails.
Monitoring
Settings > Integrations > Integration Logs records every push and pull with its outcome and the Salesforce error message when one fails. Settings > Integrations > Integration Locks lists records that failed repeatedly and are held from further attempts until unlocked; unlock a record there after fixing the underlying cause. The Sync button on the Connection tab runs a pull immediately for every enabled object.
Custom field mapping
Default field mappings appear under Mapping Rules in the integration settings, where you can view defaults, add custom field mappings, set direction (import, export, or both), and mark fields create-only. WeGive does not create fields in Salesforce; create the custom field first, then map to it. See Data Mapping Overview.