Salesforce
The Salesforce integration sends Full Fabric data to your Salesforce org. An administrator connects the org once; Full Fabric then keeps a Salesforce Lead for each profile and an Opportunity for each journey, filling their fields from mappings you choose and setting the Lead status and Opportunity stage from the person's lifecycle state. Sync runs one way, from Full Fabric to Salesforce: changes made in Salesforce are not copied back, and Full Fabric never deletes Salesforce records.
How It Works
Syncs run in the background a few moments after the change in Full Fabric.
Connecting Salesforce
- Go to Settings → Other integrations → Salesforce (in the Other group). The link only appears when the Salesforce integration is enabled for your institution.
- Click Authenticate. The Authenticate with Salesforce window asks for the Instance URL of your org, for example
https://your-domain.my.salesforce.com/. - Click Authenticate, sign in to Salesforce and approve access. Full Fabric asks for API access and a refresh token so it can keep working without you.
- Salesforce returns you to the settings page, which now shows Active and the sync cards.
The Instance URL must use https and be a salesforce.com address: login.salesforce.com, test.salesforce.com or your my.salesforce.com domain. Other addresses, including force.com ones, are refused and the connection fails with an error page.
| Card | Contents |
|---|---|
| Profile → Lead | Sync profiles toggle, Journey State to Lead Status and Profile Fields to Lead Fields mappings |
| Journey → Opportunity | Sync journeys toggle, Salesforce opportunity name, Journey State to Opportunity Stage and the Opportunity field mapping |
| Advanced | Authenticated profile ID (the Full Fabric user who connected), ID, Instance URL, Scope, and a Re-authenticate button that reopens the instance URL window |
Both toggles start off and save as soon as you click them. Mapping rows save automatically once both sides are filled. Full Fabric renews its Salesforce access automatically with the refresh token.
Warning: Do not turn on refresh token rotation for the Full Fabric connection in Salesforce. Two syncs renewing access at the same moment can then invalidate the connection, and someone has to click Re-authenticate.
Disconnecting
Click De-activate and confirm De-activate Salesforce?. This removes the connection, turns both syncs off, resets all four mappings to their required rows, and forgets which Leads and Opportunities were linked to Full Fabric records. Nothing is deleted in Salesforce.
Warning: After connecting again, profiles find their Leads again by email address, but journeys create new Opportunities: Full Fabric does not search Salesforce for existing Opportunities.
Profiles to Leads
Turn on Sync profiles on the Profile → Lead card.
Journey State to Lead Status
Salesforce Leads always need a status, while Full Fabric keeps status on each journey. Map each Full Fabric lifecycle state to a Salesforce Lead status; the Lead gets the status mapped to the most advanced lifecycle state across the person's journeys. If that state is not mapped, the Lead status is left as it is.
Profile Fields to Lead Fields
Map Full Fabric field to Salesforce field. Email, first name, last name and Company are always mapped and can't be changed; Company is filled with the person's first and last name. Only Lead fields that Salesforce allows to be updated are offered.
- Journey fields can be mapped too: their value comes from the person's most advanced journey.
- Communication policy fields use the most recent acceptance.
- Mappable field types, empty values, option set values and first UTM fields work as for HubSpot (see Profiles to Contacts), using each option's Salesforce value.
- Data that doesn't fit the Salesforce field, or a missing required field, makes the sync fail.
When Leads sync
| Event | Synced when |
|---|---|
| A profile is created | Sync profiles is on |
| A profile is updated | A mapped field changed, or a mapped journey field changed on the most advanced journey |
| A journey is added or changes lifecycle state | The new state is mapped to a Lead status and is the person's most advanced state |
| A journey's fields change | It is the most advanced journey, its state is mapped to a Lead status, and a mapped journey field changed |
| A journey is removed | It held the most advanced state and the person already has a Lead, so the Lead drops that journey's data |
| A policy is accepted | A field of that policy type is mapped |
Full Fabric finds the Lead by the link it stored on an earlier sync, otherwise by searching Salesforce Leads for the profile's email address, and creates one if none matches. If the linked Lead was deleted in Salesforce, the next sync finds or creates another.
Journeys to Opportunities
Turn on Sync journeys on the Journey → Opportunity card.
- Salesforce opportunity name: a template, by default
{{product.long_name}} - {{profile.first_name}} {{profile.last_name}}. Use Add merge field to insert fields; Example previews the result. - Journey State to Opportunity Stage: map each Full Fabric lifecycle state to a Salesforce Opportunity stage.
- Full Fabric field to Salesforce field: journey, product and profile fields; only updatable Opportunity fields are offered.
Note: Option set Salesforce values are applied to Lead fields only. Opportunity fields receive checkbox and dropdown options as stored in Full Fabric.
When Opportunities sync
| Event | Result |
|---|---|
| A journey is added or changes lifecycle state, and the new state is mapped to a stage | The Opportunity is created, or updated, with the mapped stage, name and fields |
| A mapped journey or profile field changes while the journey is in a mapped state | The Opportunity is created or updated |
| The journey is in a state with no stage mapping | Nothing is sent |
A new Opportunity gets a Close Date one week after it is created. Full Fabric sends only the name, stage, close date and mapped fields; it does not link the Opportunity to the Lead. If the linked Opportunity was deleted in Salesforce, the next sync creates a new one.
Common Failures
Salesforce sync failures are not listed in Sync management and are not retried; they are only recorded in Full Fabric's system logs. A record syncs again at its next qualifying change.
| What you see | Usual cause | Fix |
|---|---|---|
| Invalid URL under Instance URL, Authenticate disabled | The value is not a full URL | Enter the full address, starting with https:// |
| An error page after clicking Authenticate | The instance URL is not an https salesforce.com address, or access was not approved |
Use your my.salesforce.com address and approve access |
| Lead fields, Lead statuses or Opportunity stages don't load on the settings page | Salesforce rejected the stored connection, or returned an error | Click Re-authenticate |
| Leads or Opportunities stop updating | The connection was revoked, or invalidated by refresh token rotation | Click Re-authenticate |
| One record doesn't update | A mapped value doesn't fit its Salesforce field, or a required field is missing | Correct the mapping or the data in Full Fabric |
Permissions
| Action | Who can do it |
|---|---|
| Connect, configure or de-activate Salesforce | Staff with Global integrations (core.institutions.global_integration_settings), see Integrations |