Available integrations
Last updated: April 30, 2026
Available integrations
WeGive integrates with the systems your organization already uses. This article lists what's currently supported in the dashboard and what each one is for. To set one up, see Setting up an integration.
The integrations listed here are confirmed in the WeGive dashboard. New integrations get added over time, so the live Integrations page in your dashboard is always the source of truth for what's available to you.
CRMs and donor management
These integrations sync donor records, funds, and transaction history between WeGive and your donor database.
Salesforce (NPSP)
For organizations using Salesforce with the Nonprofit Success Pack. Connects via OAuth and supports two-way sync of donors, funds, and gifts. Salesforce has the deepest configuration surface area of any WeGive integration, with extensive options for field mapping and custom behavior.
Bloomerang
Connects via API key. Syncs donors, funds, and transactions in both directions. Supports a default fund ID so transactions without a designation can be routed to the right place in Bloomerang.
Raiser's Edge (NXT)
Blackbaud's flagship CRM. Connects via OAuth and uses a Client ID, Client Secret, and Subscription Key. Syncs donors, funds, and transactions.
Virtuous
Connects to Virtuous CRM for donor and gift sync.
Neon (NeonOne / Neon CRM)
Connects to Neon for donor and gift sync.
DonorPerfect
Connects to DonorPerfect for donor and gift sync.
Church management systems
These integrations are tailored for churches and faith-based organizations.
Planning Center
Connects via OAuth. Syncs people and giving data with Planning Center.
Church Community Builder (CCB)
Connects to Church Community Builder for membership and giving sync.
E-signature
DocuSign
Used for pledge agreements and other documents that require a signature workflow tied to a donation or campaign.
Other systems
Siebel
Oracle Siebel CRM integration for organizations running on Siebel.
Azure
Microsoft Azure integration, typically used for identity or cloud service connections.
What if I don't see my tool here?
If your CRM or system isn't on this list, here are your options:
Check the live Integrations page — your dashboard always reflects the current set of supported integrations, which may include tools added after this article was written.
Use Zapier or a similar middleware if WeGive doesn't have a direct integration with your tool but Zapier connects to both.
Talk to your CSM about whether your tool is on the roadmap, or whether a custom workflow can fill the gap.
For technical users
Per-integration auth methods
Integration | Auth method | Required fields |
|---|---|---|
Salesforce | OAuth 2.0 | Client ID, Client Secret |
Raiser's Edge | OAuth 2.0 | Client ID, Client Secret, Subscription Key |
Planning Center | OAuth 2.0 | Client ID, Client Secret |
DocuSign | OAuth 2.0 | Client ID, Client Secret |
Bloomerang | API key | API key, default fund ID (optional) |
Virtuous | API key | API key |
Neon | API key | API key, org ID |
DonorPerfect | API key | API key |
Exact field names and screens may vary by integration; the integration's own settings page is the source of truth.
Sync directions and entities
Most CRM integrations expose independent toggles for push and pull on each entity type. The common entity set is donors, funds, and transactions, with push_* and pull_* toggles for each. Some integrations add CRM-specific entities (custom fields, designations, campaigns).
Backend controllers
Each integration has a corresponding controller in wegive-api:
SalesforceControllerRaisersEdgeControllerBloomerangIntegrationControllerPlanningCenterControllerVirtuousIntegrationControllerNeonIntegrationControllerDonorPerfectIntegrationControllerCcbIntegrationControllerSiebelIntegrationControllerAzureIntegrationControllerDocusignIntegrationController
Each exposes some combination of update, oauth/initiate, oauth/disconnect, test, and sync endpoints, depending on the integration.
Frontend components
The corresponding Vue settings components live in wegive-dashboard-v2/src/views/integrations/, named IntegrationSalesforce.vue, IntegrationBloomerang.vue, etc. The main index page at src/views/Integrations.vue renders a tile per integration using a definition object that specifies id, settingsRouteName, and faviconDomain.