This article gives an overview of the VolunteerHub integration for Alpine.
Overview
Your Alpine database can be configured to automatically integrate with your VolunteerHub account, pulling events and constituents on a nightly basis into your database. Humanitru’s integration with VolunteerHub allows you to synchronize your VolunteerHub user data, such as contact information, event registration, and volunteer hours, automatically with your Alpine database.
What we push into VolunteerHub
Since the goal of this integration is to pull information from VolunteerHub, your Humanitru Alpine database will not push any information into your VolunteerHub account—it will only pull information.
NOTE: VolunteerHub serves as the primary source for your volunteering data. Your Alpine database does not push any data into VolunteerHub to avoid data conflicts. If you make updates to a volunteer's information in VolunteerHub (such as name or address), you must also manually update the corresponding Constituent in Alpine. Similarly, any changes made to a Constituent in Alpine will not automatically reflect in VolunteerHub.
What we pull from VolunteerHub
On a nightly basis, Humanitru Alpine will fetch a list of VolunteerHub users to sync over into your database, along with their corresponding contact information (email, name, etc.).
Constituent Mapping
|
VolunteerHub Field |
Humanitru Alpine Field |
| FirstName + LastName | [Base] Field: Name |
| MiddleName | [Custom] Field: Middle Name |
| EmailAddress | [Base] Field: Email |
| Address1 + Address2 + Address4 + City + State + PostalCode | [Base] Field: Address |
| Date of Birth | [Custom] Field: Date of Birth |
| PhoneNumber | [Base] Field: Phone |
Action Mapping
Event registrations and volunteer hours from VolunteerHub users will be synchronized into Alpine as Volunteer Hours Actions.
|
VolunteerHub Field |
Humanitru Alpine Field |
|
Event StartTime |
Happened At |
|
UserRegistrations Hours |
Hours Volunteered |
|
Event Name |
[VolunteerHub] Events |
NOTE: If any volunteer events are marked as deleted (deleted: true) in VolunteerHub, they will not be synchronized into Alpine.
Sync Details
Timing: Nightly
This integration syncs on a nightly basis, and does not occur real-time.
Constituent Matching: User Unique ID
When looking up pre-existing Constituents to match within Alpine, VolunteerHub's Unique User ID, UserUid, field will be prioritized. If no matching User ID is found, then a new Constituent will be created.
Action Matching: Yes
Every Volunteer Hours Action synced from VolunteerHub is mapped using the VolunteerHub's Event Unique ID, EventGroupUid, to reduce duplicates and improve reliability.