When a chapter (group) exists on Bevy, Bevy can create or update a Salesforce Campaign for that group. Sync runs within a few minutes of create or a mapped change. You can set the Campaign Type Bevy uses.
This page covers what happens when a Bevy chapter (group) becomes a Salesforce Campaign, including the Campaign Type Bevy sends. Connection steps stay in Salesforce integration - Connect Bevy to Salesforce. Which path your community uses is in Salesforce integration - Introduction. Campaign dates, name length, and Type prep are in Salesforce integration - Match Bevy records.
What Bevy sends when a group syncs
Bevy syncs the chapter one-way to Salesforce as a Campaign:
- On the first successful sync, Bevy creates a Campaign and stores its Salesforce ID.
- Later mapped changes update that same Campaign.
- Bevy sets Campaign Type from Campaign type for Bevy groups (default Bevy Group). If another Type value is mapped, Bevy sends that prefix, a colon, and the mapped value.
Chapter memberships become Campaign Members on that Campaign. That job is covered in Salesforce integration - Sync chapter members as leads.
When the sync runs
After a chapter is created, or after a mapped field on that chapter changes, Bevy queues the record. Salesforce usually shows the Campaign within about five minutes.
On Integration Suite, only chapters created or changed after you connect are sent. Contact Bevy Support if you need existing chapters sent.
Turn on group 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 updates as Campaigns. There is no separate Sync Bevy groups as campaigns checkbox on this path. Map at least the chapter name to Name in the wizard.
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.
- Optionally set Campaign type for Bevy groups (default Bevy Group).
- 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 chapter title, description, created date, and Campaign Type.
| Bevy field | Salesforce field | Notes |
|---|---|---|
| Chapter title | Name | Required to create the Campaign. Names longer than 80 characters are shortened and end with .... Map the chapter name to Name in the Integration Suite wizard. |
| Chapter description | Description | Sent when mapped |
| Chapter created date | StartDate | Calendar day only on the standard field. See Salesforce integration - Match Bevy records for date and time. |
| Campaign type for Bevy groups | Type | Native default is Bevy Group. Change it under General Settings → Salesforce. If another Type value is mapped, Bevy sends the prefix, a colon, and that value. |
To send more fields:
- 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.
Parent Campaign for events
When group Campaign sync is on, published and canceled event Campaigns use this chapter Campaign as their ParentId. Details are in Salesforce integration - Sync events as campaigns. If group Campaign sync is off, event Campaigns have no parent from Bevy.
Turning Connect off and back on on Integration Suite can create duplicate Campaigns for chapters and events. Avoid disconnecting unless you need to. Remove any duplicates in Salesforce.
Check a test group
- Create a test chapter, or change a mapped field on an existing chapter (for example the title or description).
- Wait about five minutes.
- In Salesforce, confirm a Campaign with that chapter title exists, or that the existing Campaign was updated, and that Type matches your Campaign type for Bevy groups setting (or Bevy Group if you left the default).
If nothing appears, confirm the connection in Salesforce integration - Connect Bevy to Salesforce, confirm group sync is on for your path, and confirm the chapter name is mapped to Name. For Campaign dates and Type prep, see Salesforce integration - Match Bevy records.