Integrations
Salesforce
Customer entities, decisions, and account history flow into the memory graph.
Object mapping
| Salesforce | Mnemos entity | Note |
|---|---|---|
| Account | Customer | One Customer per Account, keyed on 18-character Id. |
| Opportunity | Decision | Closed opportunities become Decisions with rationale fields. |
| Contact | Person | External Person entity; never merged with internal members. |
| User | Person | Internal Person, can map to a Mnemos member via email. |
| Case | Workflow | Recurring case patterns can be promoted to SOPs. |
| ContentDocument | Artifact | Attached collateral is indexed and citable. |
Sync model
Mnemos uses Salesforce Platform Events and the CDC stream for near-real-time updates, with a nightly reconciliation pass for drift. Field-level history is preserved as edits on the corresponding graph entity, so the memory graph reflects how a customer relationship evolved, not just its current state.
manual backfill
curl -X POST https://api.mnemos.ai/v1/integrations/salesforce/backfill \
-H "Authorization: Bearer $MNEMOS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"objects": ["Account", "Opportunity", "Contact"],
"since": "2024-01-01T00:00:00Z"
}'Field-level security
Mnemos uses the Connected App's OAuth scope. To prevent over-exposure, configure the App with field-level security that mirrors what an average rep can see, and rely on Mnemos role-based filtering for finer access decisions.