Fund Mapping

WeGive Funds map to Bloomerang Funds. The mapping is intentionally minimal — only two fields sync.

Record Model

WeGive record	Bloomerang record	Correlation column
Fund	Fund	`bloomerang_id`

Push (WeGive → Bloomerang)

POST fund (or PUT fund/{id} on update)
{
  "Name": <fund.name>
}

That’s the entire payload — no description, goal amount, category, active status, or sort order is sent. The returned Id is stored as the fund’s bloomerang_id.

Pull (Bloomerang → WeGive)

Funds are pulled via GET funds (50 per page, filtered by lastModified) and imported, matched on bloomerang_id:

WeGive field	Source
`bloomerang_id`	Fund `Id`
`name`	Fund `Name`

Same as push — no other field is read from the Bloomerang response.

Default Fund

There’s a configurable Default Fund ID setting, used as a fallback FundId when a transaction’s own fund hasn’t been pushed to Bloomerang yet. Nothing creates a default fund automatically — it must already exist in Bloomerang and be configured on the integration.

Matching

Matching is by bloomerang_id only — there’s no fund-name matching or duplicate-name handling in this integration.

Getting Help

WeGive Support: [email protected]
Bloomerang API Documentation: bloomerang.co/features/api

​Fund Mapping

​Record Model

​Push (WeGive → Bloomerang)

​Pull (Bloomerang → WeGive)

​Default Fund

​Matching

​Getting Help