Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

Salesforce integration - Introduction

  • Updated

Bevy's Salesforce integration syncs community data from Bevy to Salesforce, keeping your CRM current with user activity, events, and membership data.

Salesforce edition and migration status:

  • Integration Suite (Tray-based) — The newer path for eligible customers. Supports OAuth-based authentication, self-serve field mapping, and centralized integration management through the Bevy Integration Suite.
  • Native Salesforce integration — The existing path for customers on Salesforce Professional Edition, or those not yet migrated to the Integration Suite.

Supported sync objects

Both paths support a one-way sync from Bevy to Salesforce. The supported sync objects are:

  • Users — synced as Leads
  • Attendees — synced as Leads
  • Events — synced as Campaigns
  • Chapters — synced as Campaigns
  • Chapter Members — synced as Leads

Phase 1 of the Salesforce integration supports one-way sync from Bevy to Salesforce only. Bi-directional sync is not included in this release.

The following sections describe these integration options and explain how to set them up.

How does it work?

A summary of how Bevy's Salesforce integration works.

  • If we find a contact in Salesforce, we'll use it and update the contact with data we have mapped.
  • Then, we'll associate that contact with the event campaign.
  • If there is no contact, we'll search for a lead. If there is one, we'll use it, and update it with the data we have mapped.
  • If there isn't an existing lead, we'll create a new one and update the data we have mapped.
  • Then we'll associate the lead with the event campaign.
  • If an existing campaign member already exists, we'll update that record with the new changes.

You have the flexibility to dictate create/edit behavior. We support defining on a per-field basis whether it should update an existing record or not. 
Ex: If when finding an existing lead you don’t want to change the first name, we can set that up, so the first name would only be sent when creating a new lead.
If you are not wanting to replace data on existing records, Bevy has the functionality to allow defining what data should be sent to create and/or update when syncing with Salesforce.