Salesforce
AvailableOAuth
Salesforce is the system of record for many organisations, so the connection is deliberately conservative: read the objects that describe the customer relationship, and write segment membership back in a way your admin can see and control.
What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to Salesforce
- Audience segment membership, written to campaign members or a designated field on the record.
Salesforce to En Garde
- Leads, contacts, and accounts.
- Opportunities and their stage, for segmenting on pipeline position.
- Campaign objects, so En Garde reporting can line up with Salesforce campaign structure.
Connecting it
You approve the connection on the platform itself. En Garde never sees your password — the platform hands back a token scoped to the permissions shown before you approve.
- Open Integrations in your Brand Space. The page is titled Connected Apps.
- Find the platform on the Integrations tab, using the search box or the category filter.
- Click Connect. A dialog lists the permissions En Garde will request.
- Continue to the platform. A popup opens on their site where you sign in and approve. If nothing appears, your browser blocked the popup — allow popups for En Garde and try again.
- Leave the popup open until it closes on its own. En Garde then checks the connection status and the card moves to Connected.
Worth knowing
- Connect with a user whose profile has access to the objects and fields you expect to see. Field-level security in Salesforce silently hides fields from the API, which usually shows up as data that looks missing rather than as an error.
- Sandbox orgs use a different login host from production. Approving against the wrong one connects successfully to the wrong data.