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, households, companies, campaigns, funds, transactions, and pledges. Salesforce has the deepest configuration surface area of any WeGive integration, with extensive options for field mapping and custom behavior.Salesforce Nonprofit Cloud (NPC)
A separate integration from Salesforce NPSP, for organizations on Salesforce’s newer Nonprofit Cloud data model. Also connects via OAuth.HubSpot
Connects via OAuth. Syncs donors, gifts, and recurring plans with HubSpot CRM, with the most granular field-mapping options of any integration (separate mapping configuration per object: contacts, companies, households, payments, recurring plans).Bloomerang
Connects via API key. Syncs donors, funds, and transactions in both directions. Requires 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 via API key for donor and gift sync.Neon (NeonOne / Neon CRM)
Connects via API key (Org ID plus an API key) for donor and gift sync.DonorPerfect
Connects via API key for donor and gift sync.DonorDirect
Syncs donors, funds, campaigns, gifts, and recurring gifts from DonorDirect (StudioEnterprise).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. Connected at the organization level (viads_user_id/ds_account_id); individual campaign events that use DocuSign also require their own template ID configured before registration signing will work.
Fundraising and matching
Double the Donation
Automatically submits donations for corporate gift matching via Double the Donation. See How Double the Donation Matching Gifts Works for Donors for the donor-facing checkout experience and match-status flow.Automation
Zapier
Connects WeGive to thousands of other apps via Zapier’s automation platform — no in-dashboard setup screen; you connect WeGive from the Zapier side.Webhooks
Create direct event subscriptions and have WeGive post event payloads to your own endpoints — not a third-party CRM connection, but listed alongside the other integrations in the dashboard.Other systems
Siebel
Oracle Siebel CRM integration for organizations running on Siebel.Azure (Microsoft Entra ID single sign-on)
Lets your organization’s staff sign in to the WeGive dashboard using Microsoft Entra ID (Azure AD) credentials instead of a WeGive password — an SSO/identity integration, not a data-sync integration. Configured per email domain with a tenant ID, client ID, and client secret. See Setting up Azure Entra single sign-on (SSO) for your WeGive dashboard for the full walkthrough.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
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, withpush_* and pull_* toggles for each. Salesforce NPSP additionally covers households, companies, campaigns, and pledges. Some integrations add CRM-specific entities (custom fields, designations, campaigns).
Where each integration is defined
Every integration’s route, settings-route name, icon, and “is it connected” status check is centralized in one registry file:wegive-dashboard-v2/src/config/integrations-registry.ts (INTEGRATION_DEFINITIONS)
This is the authoritative list of every integration the dashboard can render a tile for — a faster and more reliable way to confirm the current full integration list than reading any individual controller.
Backend controllers
Each integration has a corresponding controller inwegive-api/app/Http/Controllers/Dashboard/, for example:
SalesforceControllerNpcControllerHubspotControllerRaisersEdgeControllerBloomerangIntegrationControllerPlanningCenterControllerVirtuousControllerNeonControllerDonorPerfectControllerCcbIntegrationControllerDonorDirectControllerDoubleTheDonationIntegrationControllerSiebelIntegrationControllerAzureIntegrationController
Dashboard/WebhookController.
Each CRM-integration controller exposes some combination of update, oauth/initiate (OAuth integrations only), oauth/disconnect, test, and sync endpoints, depending on the integration.
Frontend components
The corresponding Vue settings components live inwegive-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 by reading INTEGRATION_DEFINITIONS directly, filtering out any integration gated behind a featureFlag the organization doesn’t have enabled.