Overview
The Raiser's Edge integration syncs Donately donor and donation data to Blackbaud Raiser's Edge NXT Constituents and Gifts via the Blackbaud SKY API. It uses OAuth 2.0 with a Blackbaud subscription key for authentication.
Once connected, syncs are triggered automatically each time a donation is created, updated, or refunded in Donately.
What Gets Synced
- Constituent — Donor identity, address, email, and phone information
- Gift — Each donation, including recurring subscription details
Configuration
These settings are configured per Donately account. In addition to OAuth credentials, the integration requires a Blackbaud API subscription key.
| Setting | Description |
|---|---|
| subscription_key | Blackbaud API subscription key sent as the Bb-Api-Subscription-Key request header on all API calls |
Field Mapping
Default mappings from Donately fields to Raiser's Edge fields. These can be overridden using custom field mapping.
Constituent
| Donately Field | Raiser's Edge Field |
|---|---|
| unique_identifier | custom_constituent_dntly_person_id (custom) |
| first_name | first_name |
| last_name | last_name |
| email.address | |
| phone_number | phone.number |
| street_address | address.street |
| city | address.city |
| state | address.state |
| zip_code | address.postal_code |
| country | address.country |
Gift
| Donately Field | Raiser's Edge Field |
|---|---|
| unique_identifier | custom_gift_dntly_donation_id (custom) |
| donation_name | description |
| donation_amount | amount |
| donation_date | date |
| anonymous | is_anonymous |
| on_behalf_of | tribute.name |
| comment | comment |
| transaction_id | custom_gift_dntly_transaction_id (custom) |
| processor | custom_gift_dntly_processor (custom) |
| donation_type | custom_gift_dntly_donation_type (custom) |
| status | custom_gift_dntly_status (custom) |
| subscription_frequency | custom_gift_dntly_recurring_frequency (custom) |
| subscription_id | custom_gift_dntly_subscription_id (custom) |
Record Matching
The integration uses the following strategies to find existing records before creating new ones. Strategies are tried in order — the first match wins.
Constituent Matching
| Strategy | Description |
|---|---|
| FindByPersonId | Primary match using the Donately donor ID stored in the custom_constituent_dntly_person_id custom field |
| FindByEmailAndName | Fallback match using donor email, first name, and last name via the Blackbaud constituent search endpoint |
Gift Matching
| Strategy | Description |
|---|---|
| FindByDonationId | Match by Donately donation ID stored in the custom_gift_dntly_donation_id custom field |
Advanced
Custom Field Mapping
You can override the default field mappings with a custom mapping. Custom mappings are defined as a JSON object where keys are Donately field names and values are the target Raiser's Edge field names.
{
"Person": {
"email": "email.address",
"unique_identifier": "custom_constituent_dntly_person_id",
"phone_number": "phone.number"
},
"Donation": {
"donation_amount": "amount",
"unique_identifier": "custom_gift_dntly_donation_id"
}
}
Person— Maps donor fields to Raiser's Edge Constituent fieldsDonation— Maps donation fields to Raiser's Edge Gift fields