--- title: "How to Sync Front with Salesforce" description: "Sync Front with Salesforce so shared-inbox conversations become Contacts, Accounts, and activities, and owner or status changes come back to the inbox." canonical: https://www.stacksync.com/blog/how-to-sync-front-with-salesforce last_modified: 2026-07-21 --- # Getting Front Conversations Into Salesforce Without Retyping Them > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A practical walkthrough of connecting Front to Salesforce: what belongs in the CRM and what does not, how the sync runs from webhook to write, how senders are matched to the right Contact and Account, and exactly which fields stay in step in both directions. Author Ignacio Malpartida · GTM Engineer Published July 21, 2026 Read time 7 min read REVOPS Front holds the conversation. Salesforce holds the record. Without a sync between them, a person is the bridge: someone reads an email, opens the CRM, hunts for the Contact, and retypes what just happened. More often, nobody does, and the CRM slowly stops describing the customer. Syncing Front with Salesforce removes that step entirely. A message lands, the sender is matched to a Contact and an Account, and the conversation shows up on the right record within seconds. When the rep then changes the owner or the case status in Salesforce, the person answering the inbox sees it without switching tabs. ![Three moves to sync Front into Salesforce: connect both over OAuth, match on email and domain, then keep writing in both directions](https://www.stacksync.com/images/blog-highlights/fr-salesforce-summary.webp) Here is how to set it up, what to leave out, and what actually stays in step. For the wider picture, see the guide to an [enterprise iPaaS for Front](https://www.stacksync.com/blog/enterprise-grade-ipaas-for-front). ## Decide what belongs in Salesforce first The instinct is to sync everything. Resist it. A shared inbox carries a lot of traffic that has no business in a CRM: internal threads, vendor newsletters, recruiting mail, and the half of the inbox that is not a customer at all. Once that lands in Salesforce it is expensive to remove and it makes every report worse. Filter at the source instead. Choose which Front inboxes are in scope, exclude tags you use for internal work, and skip sender domains that are never customers. What is left is the traffic that genuinely belongs on a Contact record, which is usually a much smaller and much more useful set. ## How the sync runs, step by step The whole path from inbox to CRM is five short steps, and none of them wait for a scheduled job. A change in Front fires a webhook, the engine works out what changed, matches the customer, writes to Salesforce, and then keeps the return path open. ![The five steps from a Front thread to a Salesforce record: the thread moves, the event is caught, the sender is matched, Salesforce is updated, and changes flow back to Front](https://www.stacksync.com/images/blog-diagrams/fr-salesforce-concept.webp) *From a Front thread to a Salesforce record, and back again, in seconds.* Because the trigger is an event rather than a timer, the delay is seconds. That matters more than it sounds: a rep who opens Salesforce two minutes after a customer wrote in should see the conversation there, not on the next hourly run. ## Matching the sender to the right account Matching is where most inbox-to-CRM projects go wrong, because email addresses are messy. Someone writes from a personal address, a shared alias, or a new domain after an acquisition. The rule that works in practice is layered: try the exact email first, fall back to the company domain, and only create a new record when neither matches. ![A round-trip between Front and Salesforce: a new message is matched to a Contact and Account, logged as an activity, then owner and status changes are written back to the conversation](https://www.stacksync.com/images/blog-diagrams-mermaid/fr-salesforce-sequence.webp) *One full round-trip. Origin tags stop the write from bouncing back as a new change.* The return leg is what makes it a sync rather than a feed. A change to the owner or the case status in Salesforce is written onto the Front conversation, so the inbox reflects the CRM. Origin tracking marks which system caused each write, which is what stops the two systems from updating each other forever. ## What syncs between Front and Salesforce You choose the map, but a typical Front to Salesforce setup keeps these in step. | Front | Salesforce | Direction | | --- | --- | --- | | Sender email | Contact | Matched or created | | Sender domain | Account | Matched or created | | Conversation | Task or activity | Both ways | | Tagged as support | Case | Front to Salesforce | | Assignee | Owner | Both ways | | Conversation status | Case status | Both ways | A typical field map. Most rows are two-way, which is what keeps the inbox and the CRM telling the same story. ## Stop retyping the inbox Once Front and Salesforce are synced, the CRM fills itself from the conversations your team is already having, and the inbox shows what the CRM knows. Nobody retypes anything, and the customer history stops depending on whether someone remembered to log it. If HubSpot is your CRM instead, the same engine handles [Front and HubSpot](https://www.stacksync.com/blog/two-way-sync-solutions-front-hubspot). To add order and invoice context to the same inbox, see [Front and NetSuite](https://www.stacksync.com/blog/sync-front-and-netsuite), or [book a demo](https://www.stacksync.com/book-a-demo) and we will map your real fields on the call. FAQ ## Frequently asked questions How do I sync Front with Salesforce? Connect both to Stacksync over OAuth, map the fields you care about (sender to Contact, domain to Account, conversation to activity), and turn the sync on. Front webhooks push each change within seconds, and Salesforce edits are written back onto the conversation. How does the sync know which Contact a message belongs to? It matches the sender’s email address to an existing Contact first. If there is no match, it looks at the domain to find the Account and creates the Contact under it. You decide whether unmatched senders create a new record or wait in a review queue. Does it create a Case or just log an activity? Either, based on a rule you set. Many teams log every conversation as an activity or task and only create a Case when the thread is tagged as support. Both options attach to the same Contact and Account, so the history stays in one place. Does the sync work in both directions? Yes. Owner, status, and account field changes made in Salesforce are written onto the Front conversation, and inbox changes flow the other way. Origin tracking stops a write on one side from bouncing back as a new change. Can I keep internal threads out of Salesforce? Yes, and you should. Filter by inbox, tag, or sender domain so internal discussions, newsletters, and personal mail never leave Front. It is much cheaper to filter at the source than to clean up the CRM afterwards. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector Front integrations](https://www.stacksync.com/connectors/front) - [platform CRM synchronization](https://www.stacksync.com/crm) - [CRM synchronization guides Connect customer records across sales, marketing, and operational systems.](https://www.stacksync.com/blog#topic-crm-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Revops How to Sync Zendesk with Salesforce: A Two-Way Integration Guide 9 min read read](https://www.stacksync.com/blog/how-to-sync-zendesk-with-salesforce) [Revops Connecting Dynamics 365 Finance & Operations and Salesforce 6 min read read](https://www.stacksync.com/blog/sync-microsoft-dynamics-365-finance-operations-and-salesforce) [Revops Acumatica to Salesforce & HubSpot Integration 10 min read read](https://www.stacksync.com/blog/acumatica-salesforce-hubspot-integration) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)