Guide
Connecting Salesforce
Sync contacts and leads from Salesforce, and what this product refuses to let a sync overwrite.
A Salesforce connector pulls contacts and leads in, and pushes a small number of fields back.
Authorising it
Connect through OAuth from the connector screen. Create the connected app at https://login.salesforce.com/lightning/setup/NavigationMenus/home and set its callback to the address shown there -- this product never sees a password, and the refresh token is stored encrypted and never returned by the API.
Request offline_access. Without it the connection dies when the token expires and every sync after that fails quietly.
What syncs
Name, company, title, phone and the fields you map sync normally, in both directions.
What a sync may never do
Deliverability state is protected. Opt-out state, bounce state, complaint timestamps and the suppression lock cannot be relaxed by an inbound pull, whatever the CRM says. An incoming value that would make a contact *more* mailable is rejected, and ours is pushed back the other way.
This is the guard that matters, and it is worth being concrete about why. Without it, a nightly lead pull with "Email Opt Out" unticked resurrects every address that bounced since the last run. Nobody notices, because nothing errors -- until the domain is already burnt.
Loosening a suppression is possible, but only as an explicit action taken by a person, recorded, with a reason attached.
Field mapping
Map only what you use. Every mapped field is one more thing that can disagree between two systems, and a mapping nobody reads is a mapping nobody maintains.