Connections, data streams and mapping

1. The CRM connection

In the org that hosts Data 360, the Salesforce CRM connector reads the home org (and other orgs you connect). Find its API name:

GET /services/data/v66.0/ssot/connections?connectorType=SalesforceDotCom

Salesforce's own automation post matches on a label that starts with "Salesforce Connector". The hub's reading: match on the connection's API name instead, which you control.

2. Create a CRM data stream (one per object)

From Salesforce's February 2026 automation post:

{
  "name": "Order_Home",
  "datastreamType": "SFDC",
  "connectorInfo": {
    "connectorType": "SalesforceDotCom",
    "connectorDetails": { "name": "<connection API name>", "sourceObject": "Order" }
  },
  "dataLakeObjectInfo": { "name": "Order_Home__dll", "label": "Order_Home", "category": "Other" },
  "refreshConfig": { "refreshMode": "UPSERT", "frequency": { "frequencyType": "Minutely" } }
}

• POST /services/data/v66.0/ssot/data-streams creates it. Add sourceFields to limit the columns; validate them against the object's describe first, because a field the API user can't see fails the stream.
• Use one API user for both the describe and the stream creation, as Salesforce's post advises, so permissions match.
• Choose the DLO category deliberately. Salesforce's post uses Other. The hub's reading: Account and Contact belong in Profile (identity resolution unifies profile data), and Order and OrderItem in Engagement or Other. Confirm on an existing stream with GET /ssot/data-streams/{name} before scripting it.
• Run a stream on demand with POST …/data-streams/{name}/actions/run. The path is the community plugin's.

For accounts, people and orders, stream at least Account, Contact, Order, OrderItem and Product2. With Person Accounts, also check how person accounts arrive: Salesforce's mapping pages say nothing about them.

3. Map DLOs to DMOs

• Mapping endpoints (paths from the community plugin, reconciled to Salesforce's v67 spec):
• POST /ssot/data-model-object-mappings creates a DLO-to-DMO mapping;
• PATCH or DELETE …/{mapping}/field-mappings/{field} change single fields.
• Objects and relationships: POST /ssot/data-model-objects creates a custom DMO, and POST /ssot/data-model-objects/{name}/relationships adds a relationship.
• Capture before you script. Map once in the UI in a development org, then GET the mapping and keep the JSON. The pipeline replays captured definitions rather than guessing request bodies (guides/data360/automate-the-golden-record-pipeline.md).

Metadata types

DataStreamDefinition, DataSourceObject, DataSrcDataModelFieldMap, ObjectSourceTargetMap, MktDataTranObject and DataStreamTemplate are in Salesforce's metadata registry. They are what a data kit packages (reference/data360/automation-and-data-kits.md). The hub's reading: generate them by adding streams to a data kit, not by hand.

Failures