DonorDirect Integration Setup Requirements
Before configuring the WeGive DonorDirect integration, your organization and WeGive’s team need to complete some prerequisite access and configuration steps together. Because StudioEnterprise’s data-sync API is account-scoped rather than built for bulk export, WeGive builds and hosts a small set of custom, read-only data endpoints directly against your StudioEnterprise database in partnership with your team — this section explains what that means for setup.Prerequisites
StudioEnterprise Requirements
Administrative Access
Administrative Access
- A StudioEnterprise account with System Administration module access
- Permission to manage API Endpoints and security roles (SAWs)
- A dedicated service account for scheduled sync is strongly recommended, rather than running sync under a personal login
Database Access
Database Access
- Read/write (
db_owner) access to your StudioEnterprise business database, so WeGive’s implementation team can author the custom data-sync stored procedures your integration will use - This access is typically granted through your DonorDirect environment’s standard VPN/database access process — check with your DonorDirect account team about what’s required on your side
Data Structure
Data Structure
- An understanding of how your organization uses Projects (funds), Source Codes (campaigns), and recurring giving in StudioEnterprise
- Any custom account attributes or codes you rely on, so they can be reviewed for inclusion in the sync
WeGive Requirements
Account Access
Account Access
- WeGive organization account with admin privileges
- Access to the WeGive Dashboard integration settings
- Understanding of your WeGive fund and campaign structure
Setup Process
Because DonorDirect’s sync relies on custom data endpoints built specifically for your environment, initial setup is a joint process between your organization and WeGive:1
Access provisioning
Your DonorDirect administrator grants WeGive’s implementation team database
access to a non-production (test) environment first.
2
Custom endpoint setup
WeGive’s team builds and deploys the read-only data endpoints needed for
sync, scoped to accounts, gifts, recurring plans, funds, and campaigns.
3
Test environment validation
The integration is validated against your test environment before any
production connection is made.
4
Production access and go-live
Once validated, the same process is repeated against your production
environment, and sync is enabled.
Required Information
From StudioEnterprise
From WeGive
- WeGive organization ID
- Understanding of your existing WeGive fund and campaign structure, for mapping against StudioEnterprise Projects and Source Codes
Synchronization Preferences
Determine which data types and directions you want enabled. Pull (import from StudioEnterprise into WeGive) and push (send WeGive activity to StudioEnterprise) are configured independently per data type:Accounts
Import donor and household records from StudioEnterprise
Transactions
Sync one-time gifts in both directions
Recurring Plans
Sync sustaining/recurring giving schedules
Funds & Campaigns
Import Projects and Source Codes as WeGive funds and campaigns
Push is off by default for every data type. Your organization enables
each push direction explicitly — enabling pull alone will never write data
back to StudioEnterprise. See Configuration
Options for the
full toggle list.
Data Quality Considerations
Contact Information
Contact Information
- StudioEnterprise requires a defined “type” on every stored email, phone, and address (for example, “Home” or “Business”) — WeGive maps its fixed contact-info fields to whichever type codes your organization configures
- A contact field with no matching type configured is not sent
Gift Status
Gift Status
- StudioEnterprise’s transaction status semantics are still being finalized as part of this integration’s rollout — this section will be updated with concrete guidance once that mapping is confirmed
Next Steps
Once prerequisites and access are confirmed:Configuration Options
Learn how to configure sync settings in WeGive
Data Mapping
Understand how data is mapped between systems