Connect Bevy to Salesforce from Settings → Integrations when the Salesforce card is available. Sign in to Salesforce, choose Allow, and finish the setup wizard — including Campaign Member statuses for registration, check-in, and cancel, and optional Lead or Contact fields from the event. Communities still on the native connection in General Settings keep that path until Bevy moves them.
Use the path that matches your community. If a Salesforce card is available under Settings → Integrations, connect there. If your community is still on the native connection, use General Settings and leave that connection in place until Bevy moves you. What Bevy sends, and how records are matched, is in Salesforce integration - Introduction and Salesforce integration - Match Bevy records.
| Path | Who uses it | Where you connect |
|---|---|---|
| Integration Suite | Communities whose Salesforce card is available under Integrations | Admin dashboard → Settings → Integrations → Salesforce. You sign in to Salesforce and choose Allow. |
| Native Salesforce integration | Customers already connected this way. That includes Salesforce Professional Edition and customers on other Salesforce editions who have not been moved. | Admin dashboard → General Settings → Salesforce section. You enter the instance URL, username, password, and security token. |
Important: If your community already uses the native connection, leave it in place. Do not turn it off yourself. Bevy turns the native sync quiet only after the Integration Suite connection is verified for your community, so both do not keep writing to the same Salesforce organization. When Bevy moves you, your existing Salesforce records stay linked.
Salesforce account requirements
Use a Salesforce user that can create and update the records Bevy sends. A dedicated integration user is the simplest choice. That user needs:
- API Enabled
- The Marketing User checkbox
- Read, Create, and Edit on Leads, Contacts, Campaigns, and Campaign Members
Decide whether this connection uses Production or a sandbox. For a first connection, use a sandbox. Have someone with admin access to the Bevy community available at the same time as the Salesforce user.
Before you connect, decide the Campaign Member statuses you want for registered, checked in (Attended), and canceled (Unregistered) attendees, and for chapter join and leave. Decide how those statuses get onto new Campaigns. If a Campaign does not have the status, Salesforce stores Sent instead.
Important: The Salesforce organization you connect must not already be connected to another Bevy instance. Connecting multiple Bevy instances to the same Salesforce organization is not supported and can cause data loss. See Salesforce integration - Match Bevy records.
Connect from Settings → Integrations
Use these steps when you see a Salesforce card under Settings → Integrations.
- Log in to your Bevy admin dashboard.
- Go to Settings → Integrations at
/accounts/dashboard/#/admin/settings/integrations/. - On the Salesforce card, turn Connect on. The setup wizard opens.
- On Connect your Salesforce account, choose New authentication, name it, and pick Production or Sandbox. Sign in as the integration user and select Allow.
- Complete the field and status screens in the table below. On the Salesforce side you can type a field name, including a custom field that ends in
__c. On the Bevy side you pick from the list. - Finish the wizard. The Salesforce card shows as connected. Data begins syncing one-way from Bevy to Salesforce as people and organizers take action.
| Wizard screen | What to enter |
|---|---|
| Member fields | Map at least last name to LastName and email to Email. Salesforce needs both to create a Lead. |
| Event fields | Map at least the event title to Name. Salesforce needs it to create the Campaign. Names longer than 80 characters are shortened and end with .... |
| Chapter fields | Map at least the chapter name to Name. Long names are shortened the same way as event titles. |
| Campaign Member statuses | Enter the status names for registration, check-in (Attended), and cancel (Unregistered) for attendees, and for joining and leaving a chapter. The Campaign must define each status you enter. If you leave the chapter leaving status empty, Bevy removes the member from the chapter’s Campaign instead. |
| Attendee fields | Optional. Map Bevy attendee or event fields onto Lead or Contact fields. For each row, choose whether Bevy writes the value only when the Lead or Contact is created, only when it is updated, or both. |
If a Bevy field you need is not on the list, or you need a fixed value such as a Salesforce Record Type ID, contact Bevy Support. Bevy can add it for your community. It then appears in the wizard.
To change the mapping later, select the edit icon on the Salesforce card. The edit icon is available after the card shows as connected.
Note: Only records created or changed after you connect are sent, unless Bevy Support has arranged a backfill. Contact Bevy Support if you need existing records sent.
After you connect
On Integration Suite, after the card shows as connected:
- When an attendee registers, checks in, or cancels, Bevy updates the Campaign Member status using the names you entered for registration, Attended, and Unregistered.
- If you mapped Attendee fields, Bevy can write event values onto that person’s Lead or Contact when the registration syncs, using each row’s create-only or update-only choice.
- If a Campaign or Campaign Member is deleted in Salesforce, the next change in Bevy recreates it and stores the new Salesforce ID.
- Event and chapter titles mapped to Campaign Name that are longer than 80 characters are shortened and end with
....
How Bevy matches people to Contacts and Leads is in Salesforce integration - Match Bevy records. Object-by-object sync detail stays in the Salesforce sync articles for users, attendees, events, chapters, and chapter members.
If you are moving from the native connection:
- Enter the field mapping again in the wizard. The native mapping does not carry over.
- Bevy keeps your existing Salesforce records. Linked Campaigns, Campaign Members, and person records stay the ones you already have, instead of creating a second set.
- Leave the native connection in place. After Bevy verifies Integration Suite, the old sync goes quiet. Do not turn native off yourself.
- If you do not map a Company field, new Leads use Bevy User as the company. The native connection used N/A.
- When you map whether a member is subscribed to the Global Newsletter, Bevy updates that Salesforce field when the subscription changes. The update continues after Bevy turns the native sync off. If that field is not on the Bevy list in the setup wizard, contact Bevy Support.
Tip: Reconnecting to the same Salesforce organization keeps the Campaigns and other records Bevy already linked. Do not reconnect to a different Salesforce organization on your own — contact Bevy Support first so stored IDs can be updated.
Check that data is syncing
- Create or edit a test member with a real-looking email address.
- After about five minutes, check Salesforce. A Lead with that email should exist, or the existing Contact should be updated.
- Repeat for an event. It appears as a Campaign. An RSVP appears as a Campaign Member on that Campaign.
- Optional: check the test person in on the event, then confirm the Campaign Member status moves to the Attended name you entered.
If something does not look right:
| What you see | What to do |
|---|---|
| No Salesforce card under Integrations | Contact your Customer Success Manager. Until the card is available, use the native steps on this page. |
| The wizard opens on an error page | Refresh the Integrations page and turn Connect on again. This usually happens when a disconnect and a reconnect are done too quickly. |
| Campaign Members show Sent | That status is not on the Campaign. Add the status names you entered in the wizard to the Campaign in Salesforce. Existing members update the next time their registration, check-in, or membership changes. |
| A Campaign or Campaign Member was deleted in Salesforce | Edit the matching event, chapter, registration, or membership in Bevy. The next sync recreates the record and stores the new Salesforce ID. |
| A test record does not appear | Confirm the person has an email address. Bevy sends pending records about every five minutes. If it still does not appear, contact Bevy Support with your community, the record type, the email or record ID, and the time you made the change. |
Connect with the native Salesforce integration
Use these steps when your community is still on the native connection in General Settings. That includes Salesforce Professional Edition and customers on other Salesforce editions who have not been moved. If you do not see a Salesforce card under Integrations, stay on these steps and contact your Customer Success Manager.
- Log in to your Bevy admin dashboard.
- Open General Settings at
/accounts/dashboard/#/admin/settings/general/. - Locate the Salesforce section.
- Enter:
-
Instance — your Salesforce instance URL (for example
example.lightning.force.com) - Use sandbox — optional; check this when connecting a sandbox
- Username
- Password — set this user’s password reset policy to off or infrequent so password changes do not interrupt sync
- Security token
-
Instance — your Salesforce instance URL (for example
- Select Save Settings.
- Turn on the sync options you need in the same Salesforce section, then save again:
- Sync Bevy users as leads
- Sync Bevy attendees as leads
- Sync Bevy events as campaigns
- Sync Bevy groups as campaigns
- Sync Bevy group members as leads