Configuration Options - WeGive Documentation

All configuration lives under Settings > Integrations > HubSpot in the WeGive dashboard.

Master toggle

Setting	Default	Description
Enabled	Off	Master switch. When off, no sync occurs in either direction.

Push (WeGive to HubSpot)

Each direction can be disabled independently. All push toggles default to on once the integration is enabled.

Setting	Default	What it controls
Push supporters	On	Push WeGive supporters as HubSpot Contacts
Push households	On	Push WeGive households as HubSpot Companies with the Household label
Push transactions	On	Push WeGive transactions as Deals in the Donations pipeline
Push recurring plans	On	Push recurring plans as Deals in the Recurring Donations pipeline
Push soft credits	On	Push soft credits as Deals in the Soft Credits pipeline
Push funds	On	Push WeGive funds as line items (requires the optional line-item OAuth scopes — see Setup Requirements)
Push fund allocations	On	Push fund-allocation splits as deal line items

Pull (HubSpot to WeGive)

Setting	Default	What it controls
Pull supporters	On	Pull HubSpot Contacts into WeGive as supporters
Pull companies	On	Pull HubSpot Companies into WeGive as companies
Pull households	On	Pull HubSpot Companies tagged as households into WeGive
Pull transactions	On	Pull Deal updates from the Donations pipeline — can create new WeGive transactions, not update-only. See the Warning on Introduction.
Pull recurring plans	On	Pull Recurring Donations Deal updates — same create-capable behavior as transactions
Pull soft credits	On	Pull Soft Credits pipeline deal updates
Pull funds	On	Pull fund line items back into WeGive
Pull fund allocations	On	Pull fund-allocation line items back into WeGive

Pulls never overwrite transaction amounts or statuses in WeGive. WeGive is the system of record for financial data; pull refreshes contact context (for example, job title) and detects deletions — but see the note on Pull transactions/recurring plans above: pull is not purely a refresh operation, it can also originate new records.

Merge handling

Setting	Default	Description
Merge contacts enabled	On	When a Contact merge webhook fires in HubSpot, reassign the losing record’s data to the WeGive donor linked to the winner.
Merge companies enabled	On	Same, for Company merges.

Sync behavior

Setting	Default	Description
Address sync source	Billing	Which WeGive address populates HubSpot’s primary address fields. Set to Mailing to swap. Both addresses are always available as custom properties.
Close date mapping	Initiated date	Which date populates `closedate` on a Donation deal. Switch to completed date for ACH-heavy organizations that prefer settlement date.
Contacts with emails only	Off	When on, supporters without an email are skipped on push.
Send processing ACH as success	Off	When on, ACH transactions still processing push as Success instead of Attempted.
Pull frequency	15 minutes	Interval between scheduled pulls (1–1440 minutes).

Webhooks are not a dashboard toggle today, despite appearing as one in a prior version of this page. webhook_enabled is a real column (defaults to true on every new integration) that gates whether HubSpot’s deletion/merge webhooks are processed, but there’s no validated dashboard field to change it after connecting — it isn’t in the update endpoint’s accepted fields. If you need webhooks disabled for a specific org, that’s currently a support/engineering-side change, not self-service.

Custom field mapping

Default field mappings cover the standard WeGive supporter, company, transaction, and recurring plan models. Mapping Rules ARE dashboard-exposed (same pattern as the NPSP integration) — OrganizationController::setHubspotMappingRules() confirms this is a real, self-service endpoint, not support-managed. Add or override a field mapping under Mapping Rules in the integration settings; contacting support is not required.

​Master toggle

​Push (WeGive to HubSpot)

​Pull (HubSpot to WeGive)

​Merge handling

​Sync behavior

​Custom field mapping

Master toggle

Push (WeGive to HubSpot)

Pull (HubSpot to WeGive)

Merge handling

Sync behavior

Custom field mapping