This document is currently pre-release and is subject to change, for any questions please reach out to the RecordPoint support team.
The Salesforce Connector enables RecordPoint customers to integrate their Salesforce environment with the RecordPoint platform for compliant records management. This connector ingests Salesforce objects - including standard objects such as Accounts, Cases, Contacts, Opportunities, and Contracts, as well as custom objects - and submits them to RecordPoint to support retention scheduling, disposal, litigation hold, and sensitive content detection.
Unlike fixed-hierarchy connectors, the Salesforce Connector uses a configurable object selection model: administrators choose which Salesforce object acts as the Aggregation boundary for each connector instance, then classify related objects as Records, Binaries, or References. This makes the connector suitable for a wide range of Salesforce use cases across customer service, sales, legal, and compliance functions.
Key Capabilities
The Salesforce Connector provides:
Configurable object ingestion - any queryable Salesforce SObject (standard or custom) can be designated as the Aggregation, Record, Binary, or Reference entity for a given connector instance.
Custom object support - custom SObjects (e.g.
Invoice__c,Claim__c) are supported using the same configuration model as standard objects, enabling management of proprietary business data.Self-record pattern - the Aggregation object is submitted as both an Aggregation (container) and a Record (child of itself), enabling RecordPoint to apply retention and disposal rules directly to the Aggregation source object.
Reference field flattening - related object fields (e.g. Account name, Contact email) can be classified as References and flattened onto the self-record as custom metadata, rather than creating separate Record entities.
Binary content extraction - file attachments (via Salesforce Files / ContentVersion) and rendered text content (e.g. CaseComment body, EmailMessage body) are extracted and submitted as Binaries.
OAuth 2.0 Client Credentials Flow authentication - server-to-server authentication using a Salesforce External Client App client ID and secret, with a configured Run As user that determines the permission context for all API calls.
Salesforce sandbox and production environment support.
Configurable Object Model
Rather than a single fixed entity hierarchy, the Salesforce Connector supports an administrator-defined hierarchy constructed during setup via the Salesforce Describe APIs. Each connector instance covers one Aggregation object and its related Records and Binaries.
Object Classifications
Classification | RecordPoint Level | Behaviour |
|---|---|---|
Aggregation | Aggregation | The root business context object for the connector instance. One per connector instance. |
Record | Record | Ingested as a child Record under the Aggregation. |
Binary | Binary | Child of a Record. Content extracted as unstructured content (file bytes or rendered text). |
Reference | - | Not ingested as a separate entity. Selected fields are flattened as metadata onto the parent Record (typically the self-record). |
Ignored | - | Skipped entirely during ingestion. |
Self-Record Pattern
Because RecordPoint applies retention and disposal rules to Records (not Aggregations), each Aggregation object is submitted twice:
As an Aggregation - the business context container, with minimal core fields.
As a Record (self-record) - a child of itself, carrying full metadata and any flattened Reference fields. This self-record is the item that RecordPoint can classify and dispose of.
The self-record uses a distinct External ID (e.g. {Id}:record suffix). The selfRecordEnabled toggle controls this behaviour and defaults to true.
Example Managed Objects
Because the entity hierarchy is configured per deployment, the examples below illustrate the two most common configurations. Your deployment may differ based on the Aggregation object your administrator selects.
Example - Case as Aggregation
Case (Aggregation)
├── Case (Record - self-record, enables disposal of the Case)
│ ├── Account fields flattened (Reference - Name, Industry, AccountNumber)
│ └── Contact fields flattened (Reference - Name, Email, Phone)
├── CaseComment (Record)
│ └── CaseComment body (Binary - rendered text)
├── EmailMessage (Record)
│ ├── EmailMessage body (Binary - rendered text)
│ └── ContentVersion (Binary - file attachment)
└── Task (Record)
└── ContentVersion (Binary - file attachment)Additional Entity Types
Please contact RecordPoint support to discuss support for additional entity types or alternative Aggregation object configurations not covered by the default connector setup.