Docs Integrations Salesforce
Integrations · 02 of 04

Salesforce integration — enterprise CRM.

Salesforce is the heaviest CRM Mama integrates with. The connector handles Lead vs Account routing, custom fields, Person Account variants, and Salesforce-specific governance rules. Pro tier and above.

Time: 10 min·Updated: 2026-05-25·Audience: RevOps, SF admins·Tier: Pro+ — Salesforce-side license required

TL;DR

OAuth via Salesforce Connected App. Mama supports Sales Cloud Lightning + Classic. Auto-detects Lead vs Account model. 6 custom fields installed via a Salesforce package (admin install required). Routing rule: net-new prospects → Lead; existing accounts → Account+Contact. Two-way sync opt-in.

01Connecting

Settings → Integrations → Salesforce → Install package + Connect. The flow:

  1. Install the Salesforce package (link in the integration screen) — requires SF admin permission
  2. OAuth-connect your SF user
  3. Confirm routing — Mama auto-detects but you can override
  4. Review field mapping — defaults are sensible; tweak as needed

02The Salesforce package

Installs 6 custom fields on Lead, Account, and Contact objects:

  • Mama_Fit_Score__c — Number, 0-100
  • Mama_Signals__c — Long Text Area (JSON)
  • Mama_Brief_URL__c — URL
  • Mama_Last_Brief_Date__c — Date
  • Mama_Archetype__c — Text
  • Mama_Sync_Status__c — Picklist (Synced / Pending / Conflict)

Plus a "Mama Brief" related list on Account/Lead pages that surfaces the brief inline in SF.

03Lead vs Account routing

When Mama pushes a new prospect, it has to decide: Lead or Account+Contact?

SituationDefault routing
Account already exists in SFPush as Contact under existing Account
Account doesn't exist, but Lead doesUpdate existing Lead
Neither exists, prospect is junior (Manager-)Create as Lead
Neither exists, prospect is senior (Director+)Create as Account + Contact

Override the routing logic per-workspace from Integration settings.

04Default field mapping

Mama fieldSF destination
Brief headlineMama Brief related list entry
ICP scoreMama_Fit_Score__c
Active signalsMama_Signals__c
Brief URLMama_Brief_URL__c
Archetype nameMama_Archetype__c
Decision-makersContacts under the Account

05Two-way sync

Same options as HubSpot — opt-in. When enabled, these SF fields flow back to Mama:

  • Opportunity stage and amount → enrich Mama account context
  • Closed-won + Closed-lost outcomes → train Reply Loop archetype scores
  • Owner → mirror SF ownership into Mama for visibility
  • Account Owner changes → trigger handoff notifications

06Person Account variant

If your SF org uses Person Accounts (rare for B2B, common for B2C-leaning orgs), Mama detects this on connect and adapts routing. Person Account orgs get prospects pushed directly as Person Accounts rather than Account+Contact pairs.

Confirm Person Account detection from the integration settings — there's a one-time "Confirm SF org model" toggle.

07Common mistakes

Connecting before installing the package
OAuth alone gives Mama field access but custom fields don't exist yet — pushes fail silently. Install the package first.
Letting Mama create duplicate Leads
Enable SF's standard duplicate management rules before connecting. Mama respects those rules, so duplicates get caught.
Pushing without the Mama Brief related list on the page layout
SF admins need to add the related list to Account and Lead page layouts. Without it, the brief is pushed but invisible.
Was this page helpful?