Fin for Sales can connect directly to your Salesforce account and build a working data connector for you in minutes. Requires no API knowledge, no code, and no manual field mapping.

Pick a template, authenticate with Salesforce, and our AI generator inspects your Salesforce instance (including your custom fields) to build a fully configured connector. Review the suggested mappings, tweak anything, and add it to your setup. From then on, Fin can pull live lead context into every sales conversation — and sync qualified leads back to Salesforce.

What you can do:

📥 Enrich Lead (read)	📤 Sync Lead (write)
Fin pulls live lead context from Salesforce into your sales conversations.	Fin syncs qualified leads to Salesforce. This is an upsert: it updates the matching lead if one exists, or creates a new lead if it doesn't.

Important: set up Enrich Lead and Sync Lead together

The Sync Lead (write) connector is an upsert — it will either update an existing Salesforce lead or create a new one.
At the start of a conversation, Fin doesn't know the Salesforce lead ID. The Enrich Lead (read) connector is what resolves a returning person to their existing Salesforce record (and its lead ID).
If you set up Sync Lead without Enrich Lead, Fin can't match returning leads and will create new (duplicate) records in Salesforce. Always set up both together so writes update the right record instead of creating duplicates.

Before you start

You'll need a connected Salesforce account (you'll authenticate via OAuth during setup).

Note: Salesforce is the supported CRM for this feature. Two templates are available — Enrich Lead (read) and Sync Lead (write).

How to set it up

You connect Salesforce to Fin for Sales from the "Connected services" section in Fin AI Agent > Sales > Train > Integrations.

Step 1: Authenticate

Connect Salesforce via OAuth if you haven't already.

Step 2: Pick a template

Choose Enrich Lead from Salesforce (read) or Sync Lead to Salesforce (write). To sync leads back, set up both (see the callout above).

Step 3: Provide a test email

This runs a real query against your workspace's Salesforce so the connector can be built and tested against live data.

Step 4: Let AI generate the connector

This takes about 15–30 seconds while AI inspects your Salesforce schema, runs a test request, and assembles the connector.

Step 5: Review the field mappings

You'll see a table of Salesforce field → Intercom attribute that you can edit before confirming. Any Salesforce field that doesn't match an existing Intercom attribute is automatically mapped to a new sf_-prefixed attribute that the AI creates for you.

Step 6: Add it to your setup

Read connector: add it to enrichment — it runs at the start of each conversation.
Write connector: attach it to a routing outcome — it fires when that outcome is reached.

Note:

Sync is an upsert: Sync Lead updates the matching Salesforce lead, or creates a new one if there's no match. Pair it with Enrich Lead to avoid duplicates.
Auto-refresh: Salesforce tokens expire periodically; the connector refreshes automatically, so you don't need to reconnect each time.
Custom fields included: Fin reads your Salesforce custom fields during setup, so your tailored data can be mapped too.
Sandbox vs production: Switching a connector between a Salesforce sandbox and production is manual — edit and save the connector to point it at the other environment.

Troubleshooting

If you see…	What to do
Duplicate leads showing up in Salesforce	Sync Lead couldn't match a returning person to their existing record. Make sure the Enrich Lead (read) connector is also set up so Fin can resolve the existing lead before writing.
"No records found" when creating a connector	The test email didn't match any Salesforce record. Check that the email exists as a lead in your Salesforce.
A sync (write) fails with a "required field missing" error	Your Salesforce org requires fields that weren't collected in the conversation. Make sure those required fields are being captured for the outcome that has the write connector.
Connector stopped working after ~1 hour	Usually a Salesforce auth issue. The connector should auto-refresh and retry — if it persists, reconnect Salesforce.