When someone creates a Bevy account, Bevy can send that person to Salesforce as a Lead, or update an existing Contact or Lead with the same email. Sync runs within a few minutes of the account being created or changed.
This page covers what happens when a person creates a Bevy account and Bevy sends that member to Salesforce. 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 is in Salesforce integration - Match Bevy records.
What Bevy sends when someone creates an account
Bevy syncs the member one-way to Salesforce:
- If a Contact already exists for that email, Bevy updates that Contact.
- If there is no Contact, Bevy updates an existing Lead with that email, or creates a new Lead.
Later profile changes that Bevy maps can update the same Salesforce record. Event registrations, chapter membership, and Campaigns are separate sync jobs. They are not covered here.
When the sync runs
After someone creates an account, or after a mapped field on that member changes, Bevy queues the record. Salesforce usually shows the Lead or Contact within about five minutes. Only members created or changed after you connect are sent on Integration Suite. Contact Bevy Support if you need existing members sent.
Turn on user 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 member updates. There is no separate Sync Bevy users as leads checkbox on this path. Map at least last name and email 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 users as leads.
- 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. Company is included when it is 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 | 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:
- 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 account
- Create a test member with a real-looking email address, or edit an existing test member.
- Wait about five minutes.
- In Salesforce, confirm a Lead with that email exists, or that the existing Contact was updated.
If nothing appears, confirm the connection in Salesforce integration - Connect Bevy to Salesforce, confirm user sync is on for your path, and confirm last name and email are mapped. For duplicate emails or converted Leads, see Salesforce integration - Match Bevy records.