When someone joins a chapter (group) on Bevy, Bevy can update or create a Salesforce Lead or Contact and add them as a Campaign Member on that group’s Campaign. Status updates when they leave.
This page covers what happens when someone joins or leaves a chapter (group), and Bevy sends that person to Salesforce as a Campaign Member on the group’s Campaign. Connection steps stay in Salesforce integration - Connect Bevy to Salesforce. Which path your community uses is in Salesforce integration - Introduction. How Bevy chooses a Contact versus a Lead and duplicate emails are in Salesforce integration - Match Bevy records.
What Bevy sends when someone joins a chapter
Bevy syncs the membership one-way to Salesforce:
- Bevy matches the person to an existing Contact or Lead by email, or creates a new Lead when neither exists. See Salesforce integration - Match Bevy records for the full match rules.
- Bevy creates or updates a Campaign Member on the chapter’s Campaign, linked to that Contact or Lead.
- The Campaign Member status reflects whether the person joined or left the chapter.
The Campaign Member lands on the Campaign for that chapter (group). Chapter → Campaign sync is covered in Salesforce integration - Sync groups as campaigns. If the chapter does not yet have a Campaign in Salesforce, Bevy can still update or create the Lead or Contact, and the Campaign Member is created when the Campaign is available.
Campaign Member status
Bevy updates the Campaign Member status from the membership state:
| What happens on Bevy | Campaign Member status (default) | Native setting label |
|---|---|---|
| Someone joins a chapter | Joined | Lead/Campaign status - joined Bevy group |
| Someone leaves a chapter | Departed | Lead/Campaign status - departed Bevy group |
On Integration Suite, you enter the status names in the setup wizard. On the native connection, you set them under General Settings → Salesforce. The Campaign in Salesforce must include each status name you use. If a status is missing on that Campaign, Salesforce stores Sent instead.
On the native connection, if Lead/Campaign status - departed Bevy group is left empty, Bevy removes the Campaign Member when the person leaves instead of updating the status.
When the sync runs
After someone joins or leaves a chapter, Bevy queues the record. Salesforce usually shows the Lead or Contact and Campaign Member within about five minutes. On Integration Suite, only memberships created or changed after you connect are sent. Contact Bevy Support if you need existing memberships sent.
Turn on chapter member sync
Which controls you use depends on your connection path.
Integration Suite (Settings → Integrations → Salesforce): after you connect and finish the setup wizard, Bevy sends chapter membership updates as Campaign Members. There is no separate Sync Bevy group members as leads checkbox on this path. Enter Campaign Member status names for join and leave in the wizard. Map at least last name and email for the person.
Native Salesforce integration (General Settings → Salesforce):
- Log in to your Bevy admin dashboard.
- Open General Settings at
/accounts/dashboard/#/admin/settings/general/. - Locate the Salesforce section.
- Check Sync Bevy groups as campaigns so memberships can attach to the group Campaign (see Salesforce integration - Sync groups as campaigns).
- Check Sync Bevy group members as leads.
- Set Lead/Campaign status - joined Bevy group and Lead/Campaign status - departed Bevy group (defaults Joined and Departed).
- Select Save Settings.
Note: If your community already uses the native connection, leave it in place while Bevy moves you to Integration Suite. Do not turn native sync off yourself.
Default field mapping
By default Bevy sends first name, last name, and email for the person. Company and other profile fields are included when they are mapped.
| Bevy field | Salesforce field | Notes |
|---|---|---|
| First name | FirstName | Sent on create and update |
| Last name | LastName | Required for new Leads. Map it in the Integration Suite wizard. |
| Used to match an existing Contact or Lead. Map it in the wizard. | ||
| Company | Company | Sent when mapped. On the native connection, empty company becomes N/A when Bevy creates a Lead. On Integration Suite, unmapped company becomes Bevy User. |
To send more fields (company, social profiles, chapter role, and similar):
- Native connection: Contact Bevy Support with each Salesforce field API name and the Bevy data you want mapped. You can also set create-only or update-only behavior per field.
- Integration Suite: Map fields in the setup wizard. On the Salesforce side you can type a field name, including a custom field. On the Bevy side you pick from the list. If a Bevy field you need is not listed, contact Bevy Support.
Native field maps do not carry over when you move to Integration Suite. Enter the mapping again in the wizard.
Check a test membership
- Add a test person to a chapter that already syncs as a Campaign (or sync a test chapter first).
- Wait about five minutes.
- In Salesforce, confirm a Lead or Contact for that email, and a Campaign Member on the chapter’s Campaign with the Joined status (or the name you configured).
- Optional: remove the person from the chapter on Bevy, wait again, and confirm the Campaign Member status moves to Departed (or your configured name), or that the Campaign Member is removed if you left the departed status empty on the native path.
If nothing appears, confirm the connection in Salesforce integration - Connect Bevy to Salesforce, confirm chapter member sync is on for your path, confirm the chapter has a Campaign, and confirm last name and email are mapped. For duplicate emails or converted Leads, see Salesforce integration - Match Bevy records.