Keep Brixi and Salesforce in Sync
Keep contacts, leads, and deal data aligned between Brixi and a Salesforce org. The connector authorises once against Salesforce, lets you pick the objects and fields to sync, and then keeps the two sides aligned per the rules you set.
Entry pointAutomation → Integrations
| Article summary | Details |
|---|---|
| Requires | Account admin role in Brixi and a System Administrator profile (or equivalent) in Salesforce. |
| Where to go | Integrations → Salesforce CRM → Manage. |
Before You Connect
Run through the CRM Integrations checklist first. Specifically for Salesforce, confirm:
- The admin account has API Enabled and access to the Contact, Lead, Account, and Opportunity objects you intend to sync.
- Your Salesforce org isn't behind an IP allowlist that would block Brixi's outbound calls (or that Brixi's IPs are added).
- You know which Salesforce record type to use for each object — syncs default to the user's default record type unless overridden.
- Custom fields you need to sync are API-accessible (not hidden from the profile being used).
Salesforce sandbox and production orgs are separate connections. Authorise against the org you actually want to sync — not a sandbox if you're targeting live data.
Connect Salesforce
- In Brixi, open Integrations from the main navigation.
- Find Salesforce CRM (or filter by the CRM category).
- Select Manage on the Salesforce card.
- Select Connect Salesforce. Brixi opens a Salesforce login window.
- Sign in with the admin account and approve the requested scopes (read/write on Contact, Lead, Account, Opportunity).
- Salesforce redirects you back to Brixi. The connection status changes to Connected.
- Pick the objects to sync (Contacts / Leads / Accounts / Opportunities) and the fields per object.
- Save the configuration.
What You Should See
After connecting, the Salesforce card shows a Connection Details panel with:
- Status — Connected / Reconnect needed / Failed.
- Connected Salesforce account — the org's friendly name and instance URL.
- Connected user — the Brixi user who completed the OAuth flow.
- Last sync time — when the connector last pulled or pushed changes.
The connected user's Salesforce permissions are what the sync runs with. If that user leaves the company and their Salesforce account is deactivated, the sync stops — reconnect with a service account instead of a personal one.
What Syncs
Brixi maps Salesforce objects to its own records as follows:
| Salesforce object | Brixi record | Notes |
|---|---|---|
| Contact | Contact | Phone, email, owner, and standard demographic fields. |
| Lead | Contact (with lead type) | Created as a Contact with the appropriate lead type / status. |
| Account | Company | Linked to the contacts that belong to it. |
| Opportunity | Deal | Pipeline and stage are mapped via the stage map you configure. |
| User | User | Mapped by email so owners line up across systems. |
Activities (tasks, notes, calls, emails) are not synced by default — they remain in whichever system created them.
Field & Owner Mapping
When you save the configuration, Brixi shows two mapping screens.
Field mapping — for each Salesforce field, pick the matching Brixi field. Required Brixi fields (Name, Phone) need a Salesforce source. Optional fields can be left unmapped.
Owner mapping — Brixi matches Salesforce users to Brixi users by email. Users without a match show in an Unmapped owners list — fix them before turning on the sync, otherwise records arrive unassigned.
Map a default owner for unmapped Salesforce users — usually a sales ops account — so test records always land somewhere reviewable rather than going to the Unassigned queue.
Run a Test Sync
Never run a full sync first. Use the test flow:
- In the Salesforce connector settings, pick a test segment — either a single Salesforce report, a list view, or a small filter (e.g., records modified in the last 24 hours).
- Select Run test sync.
- Wait for the run to finish (a small segment usually takes under a minute).
- Open Contacts in Brixi and verify:
- Records have owners assigned.
- Phone and email fields are populated.
- Lead type and status match what Salesforce shows.
- Tags and custom fields are present where mapped.
- Open one record and confirm the Source is Salesforce (or your configured source).
Only proceed to the full sync after the test segment looks right.
Monitor Sync Health
After the connector is live, check it weekly:
| Where | What to look for |
|---|---|
| Integrations → Salesforce CRM | Status is Connected, last sync time is recent. |
| Reporting → Contacts | Total contacts grow at roughly the rate you expect. |
| Reporting → Deals | Deal stage distribution looks like Salesforce's. |
| Contacts list | Sort by created date and spot any obvious duplicates from the sync. |
If the status flips to Reconnect needed, the OAuth token expired or was revoked — see Disconnect or Reconnect.
Disconnect or Reconnect
Reconnect when the connector shows Reconnect needed or Failed:
- Open Integrations → Salesforce CRM → Manage.
- Select Reconnect (or Connect Salesforce if the connection is fully broken).
- Sign in with the same Salesforce account.
- Confirm the previous field and owner mappings are still correct.
- Run a small test sync before resuming the full one.
Disconnect when you no longer need the sync:
- Open Integrations → Salesforce CRM → Manage.
- Select Disconnect.
- Confirm in the dialog.
Disconnecting stops new data from arriving but does not delete the records already synced into Brixi. Plan separately for cleanup if that's what you need.
Common Issues
| Issue | What to check |
|---|---|
| Connection failed at OAuth | The Salesforce admin account doesn't have API Enabled, or your org's login restrictions (IP / 2FA flow) blocked the redirect. Try from an allowlisted IP. |
| Sync stopped after working for weeks | Token expired or the connected user was deactivated. Reconnect with a service account. |
| Wrong account connected | Connected to a sandbox instead of production (or vice versa). Disconnect and reconnect from the correct org. |
| Imported records have no owner | Owner mapping has unmapped Salesforce users. Add a default owner or map the users by email. |
| Opportunity stages look wrong in Brixi | Stage map missing or wrong. Re-check the stage map and rerun the test sync. |
| Records sync but custom fields are blank | The custom field isn't accessible to the connected user's profile, or it wasn't included in the field mapping. |
| Duplicate contacts appear | Matching field (phone / email) wasn't consistent. Use the Salesforce External Id field for the cleanest match. |
Contact support if Salesforce connects successfully but:
- Records don't sync at all after a test run.
- Status keeps flipping between Connected and Failed.
- A large segment imports but a specific object type (e.g., Opportunities) is missing.
- Field mapping save fails silently.
Include the org instance URL, the connected user, the object types involved, and a sample Salesforce record ID that should have synced but didn't.