Configuration Options
The WeGive Planning Center integration provides comprehensive configuration options to control authentication methods, data synchronization behavior, batch processing, and integration features.Authentication Configuration
Authentication Methods
Setting | Type | Required | Description |
---|---|---|---|
Authentication Type | OAuth/Legacy | Yes | Choose between OAuth 2.0 or Legacy authentication |
Enabled | Boolean | Yes | Master toggle to enable/disable the entire integration |
OAuth 2.0 Configuration (Recommended)
Setting | Type | Required | Description |
---|---|---|---|
Client ID | String | Yes | OAuth Client ID from Planning Center application |
Client Secret | String | Yes | OAuth Client Secret from Planning Center application |
Scope | String | Auto | Automatically set to ‘people giving’ |
- Enhanced security with token-based authentication
- Automatic token refresh without manual intervention
- Granular permission control
- Better audit trail and access logging
Legacy Authentication Configuration
Setting | Type | Required | Description |
---|---|---|---|
Application ID | String | Yes | Planning Center Application ID |
Application Secret | String | Yes | Planning Center Personal Access Token |
- Existing implementations using basic authentication
- Organizations preferring direct credential management
- Simple setup without OAuth flow complexity
Synchronization Controls
Data Type Configuration
Configure what types of data synchronize between platforms:Donors/People Sync
Setting | Default | Description |
---|---|---|
Push Donors | Enabled | Send WeGive donors to Planning Center as people |
Pull Donors | Enabled | Import Planning Center people to WeGive as donors |
- Creates person records in Planning Center from WeGive donors
- Updates existing people when correlation ID exists
- Syncs contact information including emails, phones, and addresses
- Maintains family and household relationships
- Imports Planning Center people to WeGive
- Respects existing donor records to prevent duplicates
- Maps person attributes to appropriate WeGive donor fields
- Includes complete contact and communication information
Transactions/Donations Sync
Setting | Default | Description |
---|---|---|
Push Transactions | Enabled | Send WeGive donations to Planning Center as donations |
Pull Transactions | Enabled | Import Planning Center donations to WeGive |
- Creates daily donation batches in Planning Center
- Organizes transactions by date for accounting purposes
- Maps payment methods and fund designations
- Automatically commits batches after successful processing
- Imports Planning Center donations to WeGive
- Includes fund designations and payment information
- Links to existing donors or creates new donor records
- Preserves donation metadata and processing details
Funds Sync
Setting | Default | Description |
---|---|---|
Push Funds | Enabled | Send WeGive funds to Planning Center as funds |
Pull Funds | Enabled | Import Planning Center funds to WeGive |
- Maintains fund naming and organizational structure
- Enables proper donation designation mapping
- Handles fund visibility and active status
- Supports fund creation for missing designations
Recurring Donations Sync
Setting | Default | Description |
---|---|---|
Push Scheduled Donations | Enabled | Send WeGive recurring plans to Planning Center |
Pull Scheduled Donations | Enabled | Import Planning Center recurring gifts to WeGive |
Advanced Settings
Required Configuration
Setting | Type | Required | Description |
---|---|---|---|
Default Fund ID | String | Yes | Planning Center fund ID for donations without specific designation |
- Must be a valid, active fund ID from your Planning Center Giving module
- Used when WeGive transactions don’t have specific fund designations
- Prevents donation processing failures due to missing fund mappings
- Should be your organization’s general operating fund
Batch Processing Configuration
Setting | Options | Default | Description |
---|---|---|---|
Batch Processing | Enabled/Disabled | Enabled | Process donations in organized batches |
Daily Batch Time | Time | 8:01 AM | When daily batches are automatically created |
Batch Commitment | Auto/Manual | Auto | Automatically commit batches after successful processing |
- Organized accounting structure in Planning Center
- Efficient processing of large donation volumes
- Automatic error handling and rollback capabilities
- Clear audit trail for financial reporting
Sync Timing Configuration
Setting | Options | Default | Description |
---|---|---|---|
Sync Frequency | Real-time/Daily/Manual | Daily | How often automatic synchronization occurs |
Incremental Sync | Enabled/Disabled | Enabled | Only sync changed data for efficiency |
- Immediate synchronization for critical updates
- Individual transaction processing as they occur
- Best for organizations requiring immediate data consistency
- Scheduled batch processing for bulk operations
- More efficient for large data volumes
- Coordinated with Planning Center batch processing workflows
Data Flow Configuration
Sync Direction Matrix
Data Type | Push (WeGive → Planning Center) | Pull (Planning Center → WeGive) | Bidirectional |
---|---|---|---|
Donors/People | Configurable | Configurable | Supported |
Transactions/Donations | Configurable | Configurable | Supported |
Funds | Configurable | Configurable | Supported |
Recurring Donations | Configurable | Configurable | Supported |
Conflict Resolution
When the same record exists in both systems: For Push Operations (WeGive → Planning Center):- WeGive data takes precedence
- Planning Center records are updated with WeGive values
- Correlation IDs prevent duplicate creation
- Planning Center data takes precedence
- WeGive records are updated with Planning Center values
- Existing relationships are preserved
Integration Features
Data Processing Options
Setting | Options | Default | Description |
---|---|---|---|
Duplicate Detection | Enabled/Disabled | Enabled | Prevent duplicate records during sync |
Contact Matching | Email/Name/Both | Method for matching existing contacts | |
Error Handling | Standard/Enhanced | Standard | Level of error handling and retry logic |
API Configuration
Setting | Default | Description |
---|---|---|
Rate Limiting | 70 requests/20 seconds | Respect Planning Center API limits |
Retry Logic | 3 attempts | Automatic retry for failed requests |
Timeout | 30 seconds | Request timeout duration |
Monitoring and Logging
Setting | Options | Default | Description |
---|---|---|---|
Log Level | Minimal/Standard/Detailed | Standard | Amount of detail in integration logs |
Performance Tracking | Enabled/Disabled | Enabled | Track sync performance and timing |
Error Notifications | Dashboard/Email/Both | Dashboard | How to receive error notifications |
Batch Reporting | Enabled/Disabled | Enabled | Generate reports for batch processing |
Payment Source Configuration
WeGive Payment Source
Setting | Value | Description |
---|---|---|
Payment Source Name | ”WeGive” | All transactions use this payment source in Planning Center |
Payment Source Type | Electronic | Designation for reporting and categorization |
- Single payment source simplifies Planning Center management
- All WeGive transactions attributed to “WeGive” source
- Payment method details maintained in transaction metadata
- Supports unified reporting across payment types
Fund Management Configuration
Fund Assignment Logic
Setting | Options | Default | Description |
---|---|---|---|
Fund Creation | Auto/Manual | Auto | Automatically create missing funds in Planning Center |
Hidden Fund Handling | Skip/Include | Skip | How to handle hidden funds in Planning Center |
Fund Validation | Strict/Lenient | Strict | Validation level for fund assignments |
- Use specific fund designation from WeGive transaction
- Fall back to default fund if no designation specified
- Create new fund if specified fund doesn’t exist (when auto-creation enabled)
- Use general fund as final fallback
Fund Synchronization
Fund Visibility:- Active funds sync bidirectionally
- Hidden funds marked appropriately in WeGive
- Deleted funds handled with proper status updates
- Fund hierarchy maintained where applicable
Recommended Configuration Approaches
Standard Configuration (Most Churches)
Purpose: Maintain Planning Center as primary system with WeGive donation data enrichment Settings:- Use OAuth 2.0 authentication for security
- Enable push for all data types to Planning Center
- Use daily batch processing for efficient organization
- Configure automatic batch commitment
- Set appropriate default fund for general donations
Bidirectional Configuration (Advanced Users)
Purpose: Keep both systems completely synchronized Settings:- Enable both push and pull for all data types
- Use real-time sync for immediate updates
- Configure enhanced error handling
- Monitor performance closely
- Implement comprehensive logging
WeGive Primary Configuration
Purpose: Use Planning Center for reporting while managing donations in WeGive Settings:- Focus on push operations to Planning Center
- Maintain Planning Center fund structure
- Use batch processing for organized accounting
- Limited pull operations for fund synchronization only
Configuration Best Practices
Initial Setup
- Choose OAuth 2.0: Recommended for new implementations
- Test Thoroughly: Use test connection before enabling sync
- Start with Push Only: Begin with WeGive → Planning Center flow
- Monitor Closely: Watch logs during first week of operation
- Validate Batches: Review daily batch processing for accuracy
Ongoing Management
- Regular Reviews: Check configuration monthly
- Performance Monitoring: Track sync times and success rates
- Error Analysis: Review and resolve integration errors promptly
- Batch Validation: Verify daily batch processing completion
- Settings Optimization: Adjust configuration based on usage patterns
Security Considerations
- Credential Rotation: Update OAuth credentials annually
- Access Control: Limit who can modify integration settings
- Audit Logging: Maintain records of configuration changes
- Data Privacy: Ensure compliance with data protection regulations
Troubleshooting Configuration Issues
Common Problems
Issue: Authentication failures- Check: Verify OAuth credentials or legacy tokens are correct
- Verify: Ensure proper scopes are configured in Planning Center
- Review: Check network connectivity and firewall settings
- Check: Verify default fund ID is valid and active
- Verify: Ensure proper permissions for batch creation
- Review: Check for data validation errors in transactions
- Check: Correlation ID mapping is working correctly
- Verify: Email matching is functioning properly
- Review: Duplicate detection settings are enabled
- Check: API rate limiting compliance
- Verify: Batch size settings are optimal
- Review: Sync frequency matches data volume needs
Configuration Validation
Required Settings Check:- Authentication credentials are valid and tested
- Default fund ID exists and is active
- All required permissions are granted
- Network connectivity is confirmed
- Field mappings are configured correctly
- Duplicate detection is working properly
- Error handling is appropriately configured
- Batch processing is functioning correctly