Skip to main content

​
Configuration Options

This guide covers the configuration options for the WeGive Blackbaud Raiser’s Edge NXT integration.

​
Authentication Configuration

​
OAuth2 Settings

Client ID
  • Description: The OAuth2 client identifier from your Blackbaud Sky API application
  • Required: Yes
  • Format: String (UUID format)
Client Secret
  • Description: OAuth2 client secret
  • Required: Yes
  • Security: Encrypted at rest, never displayed after entry
Subscription Key
  • Description: Blackbaud Sky API subscription key for API access
  • Required: Yes
  • Location: Found in your Blackbaud Developer account
Environment ID
  • Description: Your Raiser’s Edge NXT environment identifier
  • Required: Yes
  • Location: Administration > Application Settings in Raiser’s Edge NXT
Redirect URI
  • Description: OAuth2 callback URL for authentication completion — auto-configured, not user-editable.

​
Synchronization Settings

Each of the toggles below can be turned on or off independently per organization; all default to enabled. Sync frequency is not a per-object setting — see Sync Cadence below.

​
Pull Configuration (Blackbaud → WeGive)

Household constituent records are not synced by this integration — Blackbaud constituents come into WeGive as either individual donors or company/organization records.

​
Push Configuration (WeGive → Blackbaud)

Funds and campaigns referenced by a transaction need to exist in Raiser’s Edge (with the Raiser’s Edge ID linked on the WeGive side) before that transaction can sync — WeGive doesn’t create a missing fund or campaign automatically on push. Pre-create these directly in Raiser’s Edge.
Communication list / donor segment sync isn’t part of this integration.

​
Batch Mode vs. Real-Time Transaction Push

Real-time (default): each new, updated, failed, or refunded transaction pushes to Raiser’s Edge individually, as it happens. Batch mode (opt-in): individual real-time transaction pushes are suppressed. Instead, a daily scheduled job runs once per day and pushes the prior day’s new card/bank transactions — plus any that newly failed or were refunded — to Raiser’s Edge as a single named gift batch ("WeGive Import <date>"), tied to your organization’s own timezone day boundary.
Donor and company pushes always happen in real time regardless of this setting — batch mode only affects transaction push timing.

​
Sync Cadence

Blackbaud pulls run on a fixed platform-wide schedule — every 15 minutes for every organization with the integration enabled. There’s no per-organization frequency setting to adjust this interval.

​
Constituent Matching

Constituent matching between WeGive and Blackbaud is by Raiser’s Edge ID — an exact match on the stored constituent ID from a prior sync, with no name/email/phone fallback. This means duplicate prevention covers records created through the WeGive integration; a gift or constituent created in Blackbaud through another channel (e.g. a manually staged CSV import) has no shared identifier for WeGive’s sync to recognize.

​
Field Mapping

Field mapping for constituents, gifts, recurring gifts, funds, companies, households, and appeals is set up automatically with a default rule set when the integration is first connected.
Push-side campaign attribution runs through Appeals, not Campaign ID — see Campaign Mapping and Gift Mapping for the specifics. If you’re configuring this integration for campaign-level reporting on pushed gifts, link your campaign fundraisers’ Appeals rather than relying on Campaign ID alone.
Default payment-method mappings:

​
Retry Behavior

Failed API requests retry automatically with exponential backoff (a handful of attempts) as a fixed platform policy — this isn’t a per-organization tunable setting.

​
Getting Help

For configuration assistance: