Skip to main content
One-time transactions push as Deals in the Donations pipeline that WeGive provisions during setup. Financial fields (amount, status/stage, dates) are push-only — WeGive is the system of record for those and they’re never overwritten on pull. Several linkage/context fields, however, are genuinely read on pull too (see the Warning under Linkage and Context below) — “all fields are push only” is not quite accurate as a blanket statement for this object.

​
Core fields

​
Linkage and context

wegive_fund_id, wegive_fund_code, and wegive_fund_name are read on pull, not just written on push — a deal (or an unattributed line item) pulled into WeGive resolves its fund designation from these three properties in that priority order (ID first, then the normalized fund code, then an exact name match), the same resolution used for recurring-plan deals. If a deal states a fund reference in any of these three properties that doesn’t resolve to a WeGive fund, the gift still imports (undesignated) but a warning is logged in the integration log’s Details tab — check there before assuming an undesignated import failed silently.

​
Payment method mapping

donor and user source types (WeGive-internal payment sources with no Salesforce/HubSpot equivalent) map to no value and never write wegive_payment_method on push.

​
Associations

Each Donation deal associates to the supporter’s Contact (once it has a HubSpot ID) and to the supporter’s Company or Household when applicable. If the supporter has not yet pushed, the deal is created without an association and linked on the next sync.