When you publish an event on Bevy, Bevy can create or update a Salesforce Campaign for that event. Sync runs within a few minutes of publish or a mapped change. Draft events do not sync.
This page covers what happens when a published Bevy event becomes a Salesforce Campaign. 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 you publish an event
Bevy syncs the event 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.
- When chapter Campaign sync is on, the event Campaign’s parent is the chapter’s Campaign.
Registrations become Campaign Members on that Campaign. That job is separate from this page.
Which events sync
Bevy syncs events that are Published or Canceled. Draft and pending events do not sync. Hidden events still sync when they are published or canceled.
After you publish, or after a mapped field on that event changes, Bevy queues the record. Salesforce usually shows the Campaign within about five minutes. On Integration Suite, only events created or changed after you connect are sent. Contact Bevy Support if you need existing events sent.
Turn on event 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 event updates as Campaigns. There is no separate Sync Bevy events as campaigns checkbox on this path. Map at least the event title 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 events as campaigns.
- Optionally set Campaign type for Bevy events (default Bevy Event).
- 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 title, short description, status, published date, end date, and Campaign Type.
| Bevy field | Salesforce field | Notes |
|---|---|---|
| Event title | Name | Required to create the Campaign. Names longer than 80 characters are shortened and end with .... Map title to Name in the Integration Suite wizard. |
| Short description | Description | Sent when mapped |
| Event status | Status | Bevy sends Published or Canceled when that status syncs |
| Published date | StartDate | Calendar day only on the standard field. See Salesforce integration - Match Bevy records for date and time. |
| End date | EndDate | Calendar day only on the standard field |
| Campaign type for Bevy events | Type | Native default is Bevy Event. 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
When Bevy also syncs the chapter as a Campaign, the event Campaign’s ParentId is that chapter Campaign. If chapter Campaign sync is off, the event Campaign has 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 event
- Publish a test event (or cancel a published test event if you are checking Status).
- Wait about five minutes.
- In Salesforce, confirm a Campaign with that event title exists, or that the existing Campaign was updated.
If nothing appears, confirm the connection in Salesforce integration - Connect Bevy to Salesforce, confirm event sync is on for your path, and confirm the event title is mapped to Name. For Campaign dates and Type prep, see Salesforce integration - Match Bevy records.