Home / Integrations / Salesforce
Native integration · live OAuth install · 90 seconds Read-only by default

Mama plugs into Salesforce the way a rep wishes everything did.

OAuth in 90 seconds. Read-only by default — we pull your Account list and write nothing until you opt in. Once write-back is on, the score, brief, and signals land on a custom field on the Account object so every rep sees them in the place they already work.

Connect Salesforce → Salesforce admin docs ↗
OAuth · 2.0
Reads Account, Contact, Opportunity
Writes 1 custom field, opt-in
Sync cadence Every 6 hours
API calls Bulk API 2.0 · low quota use
Editions Pro, Enterprise, Unlimited
What Mama writes back

Four pieces of data, all on the Account object.

No new objects, no schema migration, no Apex install. Mama writes to one custom field (or four — your call) on the existing Account record. Reps see it on the layout they already use. RevOps builds reports off it like any other Salesforce field.

Always on
Mama Score
Integer 0–100 from the ICP rubric. Updates every 6 hours. Build views, reports, and forecasts off this field just like you would Opportunity Amount.
Field:Mama_Score__c · Number(3,0)
Opt-in
Brief Summary
4-line synthesis of why the account is scored what it is — written in plain English, refreshed when the score moves >10 points. Full brief lives in Mama; this is the at-a-glance for the rep.
Field:Mama_Brief_Summary__c · Long Text Area(1024)
Opt-in
Last Signal Date
Timestamp of the most recent signal Mama detected on this account. Use in Salesforce flows to auto-route fresh accounts to the rep on call, or pause sequences when nothing has fired in 60+ days.
Field:Mama_Last_Signal__c · DateTime
Opt-in
Brief Link
URL to the full brief in Mama — score breakdown, all signal evidence, contacts, draft opener. One-click from the Salesforce record to the rep's working surface. Render as a hyperlink in the layout.
Field:Mama_Brief_URL__c · URL(255)
Install in 5 steps

90 seconds from click "Connect" to first scoring run.

No managed package, no Apex code, no admin certification required. The whole install is OAuth + a few clicks in Salesforce Setup. Your IT team can review every step in our security posture before approving.

1
Click "Connect Salesforce" in Mama
From your workspace settings. Pick your org (production or sandbox).
~ 5 sec
2
Salesforce OAuth screen
Standard Salesforce login. Approve the read scopes we request (Account, Contact, Opportunity).
~ 30 sec
3
Pick what to score
Choose Account view filter — "All", "Open opportunities", or any saved Salesforce list view.
~ 15 sec
4
Opt in to write-back (optional)
If yes, Mama creates the 4 custom fields automatically. If no, we score read-only.
~ 10 sec
5
First scoring run
Mama pulls every Account that matches your filter. First brief lands in your inbox ~3 min later.
~ 3 min
What's supported, what's not

The honest list of what we do and don't.

We try not to leave the gotchas for the install flow. Everything below is true as of the latest /changelog entry. If something on the "doesn't" list matters to you, email [email protected] — most missing things are on the roadmap.

Mama does
  • All Salesforce CRM editions — Pro, Enterprise, Unlimited, Developer. Both Lightning and Classic UI.
  • Sandbox + production orgs — install on a sandbox first, promote to production in one click.
  • Bulk API 2.0 for writes — efficient quota use, doesn't compete with your reps' API calls.
  • Salesforce list views as the source — pick any saved view in your org to scope what Mama scores.
  • Custom field creation handled automatically — Mama creates the 4 fields with your approval, you don't write a single line of Apex.
  • Multi-org workspaces (Pro) — consultancies running 8 client orgs get 8 separate Mama workspaces under one bill.
  • OAuth refresh handled automatically — tokens refresh on schedule, you never re-auth unless your admin revokes.
Mama doesn't (yet)
  • Salesforce Essentials. The Bulk API isn't available on that edition. Coming Q3 2026 via the regular REST API for small orgs.
  • Person Accounts. We score the Account object only. Person Accounts (B2C orgs) are on the roadmap but not live yet.
  • Custom-object scoring. We score Accounts, not your custom objects. If your Opportunity-equivalent is a custom object, ping us.
  • Write to multiple custom fields beyond the 4 above. Some teams want score-by-dimension split out — coming Q2 2026.
  • Real-time score push. Sync is every 6 hours, not webhook-on-change. Real-time on the roadmap for Pro tier.
  • Marketing Cloud or CDP write-back. Sales Cloud only for now. If you need MC, tell us.
Your Salesforce data never leaves your Mama workspace. Read with OAuth, AES-256 at rest, TLS 1.3 in transit, never used for training. SOC 2 Type II report under NDA. You can revoke Mama's OAuth grant from Salesforce Setup → Connected Apps any time — sync stops within the next cycle.
AES-256 TLS 1.3 OAuth 2.0 SOC 2 II (NDA)
Full security posture →
Salesforce-specific FAQ

The questions Salesforce admins ask on the first call.

Pulled from the actual evaluation conversations we've had with launch partners running Salesforce. If your question isn't here, email [email protected] and we'll add it to this page next.

Do you need a managed package?
No. Mama installs as a Connected App via OAuth. No package install, no metadata to review, no Apex. The 4 custom fields are created via the Tooling API with your admin's approval at install time.
What permission set do reps need?
None — reps see the Mama fields if they already have read access to the Account record. RevOps gets a one-click way to add the fields to a page layout.
How does this affect our API quota?
Mama uses the Bulk API 2.0 for both reads and writes. A 10,000-account org consumes ~12 bulk calls per day — negligible against typical 100k+ daily quotas. Full breakdown in our security doc.
Can I install on a sandbox first?
Yes — recommended for orgs over 10k accounts. One-click promote from sandbox to production once your IT and RevOps team have signed off. The Connected App ID is the same; only the org URL changes.
What happens if I revoke OAuth?
Sync stops within the next 6-hour cycle. The 4 custom fields remain on your Account object with their last-written values — nothing gets deleted. You can re-install any time and pick up where you left off.
Does this work with Salesforce CPQ / Sales Engagement?
CPQ: yes, transparently — we don't read or write to CPQ objects. Sales Engagement: Mama feeds Sales Engagement cadences via the Brief URL field — reps click through from the cadence step into the full brief.
Not on Salesforce?

Mama plugs into the rest of the stack the same way.

Same OAuth + read-only-by-default + one-custom-field write-back pattern across every native integration. See the full list or jump straight to one of the other big four below.

HubSpot
Native · live
Same custom-property write-back pattern. OAuth, all hubs supported.
Pipedrive
Native · live
Organization-level custom field. Webhooks supported on Pro.
Outreach
Native · live
Briefs auto-push into sequence steps. Native account-level integration.
Salesloft
Coming Q3
In active dev. Email us if you'd be a design partner.
90 seconds to install

Connect your Salesforce org and see every account scored by tomorrow morning.

Free up to 100 accounts. No credit card. Read-only by default — your IT team can audit every scope we ask for before they approve.

Connect Salesforce → See it on mock data first