Skip to content

Configuration Options

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

Master toggle

SettingDefaultDescription
enabledfalseMaster switch. When off, no sync occurs in either direction.

Push (WeGive → HubSpot)

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

SettingDefaultWhat it controls
push_donorstruePush WeGive donors as HubSpot Contacts
push_householdstruePush WeGive households as HubSpot Companies (with the Household label)
push_transactionstruePush WeGive transactions as Deals in the Donations pipeline
push_scheduled_donationstruePush recurring plans as Deals in the Recurring Donations pipeline

Pull (HubSpot → WeGive)

SettingDefaultWhat it controls
pull_donorstruePull HubSpot Contacts into WeGive as donors
pull_companiestruePull HubSpot Companies into WeGive as companies
pull_householdstruePull HubSpot Companies tagged as households into WeGive
pull_transactionstruePull Deal updates to refresh transaction metadata
pull_scheduled_donationstruePull Recurring Donations Deal updates

Sync behavior

SettingDefaultDescription
address_sync_sourcebillingWhich WeGive address pushes to HubSpot’s primary address fields. Set to mailing to swap.
closedate_mappinginitiated_atWhat date populates HubSpot’s closedate on a Donation deal. Switch to completed_at for ACH-heavy orgs that prefer settlement date.
contacts_with_emails_onlyfalseWhen true, donors without an email are skipped on push.
send_processing_ach_as_successfalseWhen true, ACH transactions in processing status push to HubSpot as Success instead of Attempted. Useful if you treat ACH as effectively cleared.
pull_frequency15Minutes between scheduled pulls.
webhook_enabledtrueListen for HubSpot deletion webhooks to clear linkages. Disable if you sync HubSpot from another system.

Custom field mapping rules

Default field mappings cover the standard WeGive donor model. If you need to push a non-standard field (e.g., a custom donor attribute to a HubSpot custom property), open a support ticket — we’ll add a NeonMappingRule to your integration that overrides the default mapping for that field.