How to Integrate Salesforce with Front

What the integration actually does

Front's Salesforce integration has two distinct halves, and it's worth separating them before you touch a setting.

The first half is the sidebar plugin. Once enabled, a Salesforce icon appears in Front's app switcher on the right of any conversation, and from there teammates can, per Front's guide to enabling and using the integration, "view and update information from Contacts, Accounts, Opportunities, and related custom objects." You can also view and create active customer support cases tied to the contact, plus see Leads, Tasks, and Notes. This half works for the whole team the moment an admin turns it on — no per-agent setup.

The second half is the optional data sync — Contacts sync and Accounts sync. These pull Salesforce records into Front's own contact and account layer so that CRM fields become usable in rules, analytics, and search. Crucially, both are one-way, Salesforce → Front: Front's accounts sync documentation states plainly that "Accounts are synced one-way from Salesforce to Front," while noting Front "maintains a live, real-time sync with Salesforce, so your accounts are always up-to-date." The sync is gated to the Professional plan and above.

Before you start

You need Front company admin permissions. Per Front's documentation, "You must have Front company admin permissions to set up the integration." You'll also need a Salesforce account with API access (the data sync and rule actions consume Salesforce API calls — more on that limit below) and login credentials for the Salesforce org you want to connect. If your Front plan is below Professional, you can still install the sidebar plugin, but the Contacts/Accounts sync that powers rules and analytics won't be available.

Step-by-step: enable Salesforce in Front

1. Open the App Store. Click the Settings gear, go to Company settings, and select App store from the left menu.
2. Find Salesforce. Search or scroll to the Salesforce app (it sits in the CRM & Ecommerce category, built by Front) and open its overview page.
3. Click Enable. This is the connect/overview screen shown below — the starting point, not a finished sync.

1. Authenticate with Salesforce. After Enable, Front hands off to Salesforce to authorize the connection using your Salesforce credentials. This step lives on the Salesforce side of the handshake — the deep field/data configuration happens in the partner account, not on the Front overview page above.
2. Choose what to sync. During setup you can turn on Contacts sync and/or Accounts sync (Professional+). Only enable what you'll actually use — every synced object costs Salesforce API calls.
3. Confirm the sidebar. Open any conversation, click the Salesforce icon in the right-hand app switcher, and check that contact, account, and case data resolves.

That's the whole install. The sidebar is live immediately; a first-time account sync can take a while to backfill, since Front supports "syncing a maximum of 500k accounts," per its accounts documentation.

What syncs, and in which direction

The single most common misunderstanding is expecting a two-way sync. It isn't one. Here's the honest breakdown:

The nuance worth internalizing: the bulk sync (Accounts, Contacts) flows one way into Front's data layer so rules can read it, but the sidebar plugin lets a teammate update a record or create a case, and those specific edits push back to Salesforce. So it's "one-way sync + interactive write-back via the sidebar," not a mirrored two-way replication. If you need genuine deep field-level two-way syncing of custom fields, Front's own guide to leveraging CRM data via rules is explicit that it takes development resources and Front's contact API endpoints to maintain — it's a build, not a checkbox.

Leveraging Salesforce data in Front rules

This is where the integration earns its keep. Once accounts and contacts are synced, their fields become conditions and actions in Front's rule engine, so your shared inbox can route by CRM value instead of guesswork.

Route by account value. Front's accounts documentation notes you can "automatically assign and route conversations in Front using account data from Salesforce." A practical rule: When an inbound message is received, If the contact's account tier is Enterprise, Then assign to the strategic-accounts group and add a VIP tag. Now your highest-value customers skip the general queue.

Push activity back to Salesforce. Front exposes rule actions that write to the CRM: Create lead in Salesforce, Send Task to Salesforce, and Send Email to Salesforce (logging the message as a completed activity). A support conversation from an unknown sender can auto-create a lead; a sales reply can log itself against the record without anyone opening Salesforce.

Segment analytics and search. Because synced fields land in Front's search and analytics, you can filter conversations by account or contact attributes — response times for your top accounts, volume by geography, and so on.

The honest limits — where it breaks down

The native integration is genuinely good, and for surfacing CRM context in the inbox it's the right tool. But there are three seams to know about before you rely on it.

Rejected credentials silently break your rules. Per Front's documentation, "If your integration credentials are rejected by Salesforce... you will see errors in Front." When the connected user's password rotates, MFA changes, or the Salesforce user is deactivated, the token dies — and any rule that reads or writes Salesforce data stops firing. The fix is admin-only: a Front company admin has to update the integration credentials in the Salesforce integration settings. Guard against it by connecting through a dedicated Salesforce integration user with a non-expiring password rather than a personal login.

The Salesforce API request limit is a real ceiling. Front is explicit: "if your company hits the API request limit you have for Salesforce, your rules will fail." Every sidebar lookup, every sync, and every rule action consumes Salesforce API calls, and your Salesforce org has a daily API quota tied to your edition and license count. A busy inbox with chatty rules can exhaust it — Salesforce returns the classic REQUEST_LIMIT_EXCEEDED error and your automations go dark until the 24-hour window resets. Front's guidance: increase your Salesforce request limit or wait for the quota cycle to start over. In practice, sync only the objects you need and keep rule actions lean.

It's one-way for bulk data. The sync reflects Salesforce into Front; it doesn't turn Front into a CRM. Changes made deep in Front (outside the sidebar's supported write-backs) don't flow to Salesforce, and true custom-field two-way sync is a development project. For a wider view of what plays well with the inbox, see the best Front integrations roundup and how they slot alongside your Front channels.

Where an AI layer picks up

The integration puts Salesforce data next to the conversation. It still takes a human to read the account, understand the question, and write the answer. That's the gap an AI agent layer closes — and it's exactly the kind of work the broader category of AI agents for customer service exists for.

Macha is one such layer. It runs on top of the Front you already use through the live Macha–Front connector — it never replaces Front, your shared inboxes, or this Salesforce integration. Instead of a teammate reading the synced account panel and typing a reply, Macha's agent reads the routed conversation, understands intent, and can reach into your systems through a custom tool that turns a REST API — including Salesforce's — into something the agent can call: fetch the live account status, look up the open case, and draft or send a grounded reply. Front's rules get the right conversation to the right place with the CRM context attached; the agent then actually resolves it. If you want the mechanics, connecting Front to Macha to route conversations to AI walks through it, and Macha's credits are consumed per AI action — never per resolution. For how inboxes fit together as a system, the Front shared inbox model is the wider picture.

FAQ

How do I enable the Salesforce integration in Front? Open Settings → Company settings → App store, select Salesforce, and click Enable, then authenticate with your Salesforce credentials. You must have Front company admin permissions. The sidebar plugin works for everyone immediately; the Contacts/Accounts data sync is a Professional-plan-and-above option you turn on during setup.

Is the Front–Salesforce sync one-way or two-way? The bulk Accounts and Contacts sync is one-way, Salesforce → Front — it reflects CRM data into Front so rules, search, and analytics can use it. The sidebar plugin lets teammates view and update records and create cases, and those specific edits write back to Salesforce. Full custom-field two-way syncing requires development work using Front's contact APIs.

Why did my Salesforce rules suddenly stop working in Front? Almost always one of two causes: your integration credentials were rejected (a company admin must update them in the Salesforce integration settings), or you hit your Salesforce API request limit and Front's rules failed. For the quota, increase your Salesforce request limit or wait for the daily cycle to reset.

What Salesforce data appears in the Front sidebar? Contacts, Accounts, Opportunities, and related custom objects — plus Leads, Tasks, Notes, and customer support Cases (which you can view and create against the contact) — all inside the Salesforce plugin in Front's right-hand app switcher.

Can I add AI on top of the Front–Salesforce integration? Yes. An AI agent layer like Macha connects to Front as a live connector alongside your existing integrations. Your rules keep routing and surfacing Salesforce context; the agent reads the conversation, pulls live CRM data through a custom tool, and drafts or sends a grounded reply.

Ready to turn "CRM context in the sidebar" into "actually answered"? Start a free trial of Macha and connect it to your Front in minutes.