Salesforce Integration

Overview

PurposeTech integrates with your organisation's own Salesforce instance to keep volunteer records, jobs, shifts, and assignments in sync. The integration is two-way — changes in either PurposeTech or Salesforce are reflected in the other, so your CRM stays up to date without manual data entry.

Salesforce is your tool — PurposeTech connects to it on your behalf. Data flows directly between PurposeTech and your Salesforce environment. PurposeTech does not store a copy of your Salesforce data beyond what's needed for the sync.

What it does

At a high level, the integration keeps these records in sync:

• Volunteers ↔ Contacts — volunteer profiles flow between PurposeTech and Salesforce
• Jobs ↔ Custom objects — collection sites, locations, and roles stay aligned
• Shifts ↔ Custom objects — time slots and capacity data
• Assignments ↔ Junction objects — who's assigned where, including status changes and cancellations
• Areas and regions — imported from Salesforce to structure your campaign geography

Sync is incremental — only records that have changed since the last sync are processed, keeping it fast even for campaigns with thousands of volunteers.

How it works

Once configured, sync runs automatically on a scheduled basis. You can control the sync direction per integration:

• Two-way — changes in either system are synced
• One-way import — pull data from Salesforce into PurposeTech
• One-way export — push PurposeTech data back to Salesforce
• Paused — temporarily stop syncing without disconnecting

Conflicts (e.g., a required field missing in Salesforce, a duplicate record) are logged in the admin portal for your team to review and resolve.

Why organisations use it

• No double data entry — volunteer records created in PurposeTech automatically appear in Salesforce
• Accurate reporting — post-event data (attendance, hours, assignments) flows back to your CRM for donor and volunteer reporting
• Bulk job import — if your sites and locations are managed in Salesforce, import them directly instead of recreating them manually
• Single source of truth — your CRM remains the master record for volunteer relationships

Data handling

• Your Salesforce, your data — PurposeTech connects to your organisation's Salesforce instance via OAuth. Salesforce is not a PurposeTech sub-processor; it's a tool you control
• Sync scope — only the mapped fields and objects are synced. PurposeTech does not read or write to Salesforce objects outside the integration configuration
• Credentials — OAuth tokens are encrypted at rest and scoped to the minimum permissions required
• Conflict logging — sync conflicts and errors are logged in the PurposeTech admin portal with timestamps, not in Salesforce
• Disconnecting — you can pause or fully disconnect the integration at any time from the admin portal. Disconnecting does not delete data in either system

Getting started

Because every Salesforce instance is different, we work with your team to:

1. Map your data model — identify which Salesforce objects and fields correspond to PurposeTech records
2. Configure the connection — set up OAuth authentication between the systems
3. Test with a sandbox — run the integration against a Salesforce sandbox before going live
4. Go live — enable sync on your production environment with monitoring

This is typically done during onboarding and takes 1–2 sessions with our team.

Next steps

• Organisation Setup — tenant configuration
• User Management — manage admin users and roles