> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt > Use this file to discover all available pages before exploring further. # Salesforce Data 360 Pipeline Connector | Collate Pipeline Integration > Connect Salesforce Data 360 (formerly Data Cloud) pipelines to Collate for Data Streams, Calculated Insights, and Data Transforms, including lineage, status, and metadata. export const ConnectorDetailsHeader = ({name, icon, stage, availableFeatures, unavailableFeatures = [], availableFeaturesCollate = []}) => { const showSubHeading = availableFeatures?.length > 0 || unavailableFeatures?.length > 0 || availableFeaturesCollate?.length > 0; const totalAvailableFeatures = [...availableFeatures || [], ...availableFeaturesCollate || []]; return
{icon &&
{name}
}

{name}

{stage}
{showSubHeading &&
Feature List
{totalAvailableFeatures.map(feature =>
✓ {feature}
)} {unavailableFeatures.map(feature =>
✕ {feature}
)}
}
; }; Use this guide to configure the Salesforce Data 360 pipeline connector. The Salesforce Data 360 pipeline connector brings data movement and processing objects from Data 360 (formerly Data Cloud) into Collate as pipelines: * **Data Streams** * **Calculated Insights** * **Data Transforms** Collate uses three separate agents for this connector. The Metadata agent ingests pipeline definitions and tags, the Usage agent ingests Pipeline Status, and the Lineage agent ingests relationships to the tables each pipeline reads from and writes to. Collate ingests only objects with an `ACTIVE` status. Configure and schedule Salesforce Data 360 workflows from the Collate UI: * [Requirements](#requirements) * [Requirements for Lineage](#requirements-for-lineage) * [Metadata Ingestion](#metadata-ingestion) * [Troubleshooting](/connectors/pipeline/data360/troubleshooting) ## Requirements Collate connects to Salesforce Data 360 through the Salesforce REST API using a **connected app** that authenticates with the OAuth 2.0 client credentials flow. Complete the following: * Configure a Salesforce connected app for the OAuth 2.0 **client credentials** flow. This gives you the **Consumer Key** and **Consumer Secret** that Collate uses to authenticate. See the Salesforce documentation on [creating a connected app](https://help.salesforce.com/s/articleView?id=sf.connected_app_create.htm) for the setup steps. * Grant the connected app the **Manage Data Cloud** and **Access Data Cloud APIs** scopes so it can list Data Streams, Calculated Insights, and Data Transforms and read their run history. * Give the integration user permission to view these objects. The connection test verifies this by listing each object type. ### Requirements for Lineage Lineage connects each Data 360 pipeline to the tables it reads from and writes to. For Collate to resolve those tables, ingest the **Salesforce Data 360 database** first with the Data 360 database connector. Then point this pipeline service to it using the **Data 360 Database Service Name** field. Data Streams can pull from upstream systems outside Data 360, for example an S3 bucket or a Snowflake warehouse. To draw lineage to those upstream tables, use **Service Mapping** to map each Data 360 connector or data source name to the Collate service that already holds it. ## Metadata Ingestion To ingest metadata from Salesforce Data 360, you need to create a service connection. The service connects Salesforce Data 360 with Collate. Once you create a service, Collate automatically starts ingesting metadata. ### Step 1: Add New Service Open the Services page and start a new service. 1. Navigate to **Settings** > **Services** and select the **Pipelines** service. Navigate to Services 2. Click **Add New Service**. Add New Service ### Step 2: Select a Service and Connector From the service type dropdown, select **Pipeline Services**, then click the **Salesforce Data 360 Pipeline** connector tile. Select Service ### Step 3: Add Service Name and Description * Enter a unique, descriptive **Service Name**. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other Salesforce Data 360 services you are ingesting metadata from. * Optional: Enter a **Description** for the service. Add New Service Name **Note**: The service name can't be changed after you set it. ### Step 4: Configure Connection Options Specify where ingestion runs, provide your source credentials, and verify the connection. #### Select Ingestion Runner Select an **Ingestion Runner**: the runner where the ingestion pipeline will execute. Add Name and Select Ingestion Runner #### Enter Connection Details Enter the connection details for Salesforce Data 360. The right-hand panel in the UI displays inline help for each field. Configure Service Connection * **Salesforce API Version**: The Salesforce REST API version to call. Defaults to `63.0`. Change this only if your Salesforce org requires a different version. * **Salesforce Domain**: The domain of your Salesforce instance, used to build the login URL. Defaults to `login`. Use `test` for a sandbox, or your My Domain subdomain for a custom domain. * **Data 360 Database Service Name**: The name of the Salesforce Data 360 database service in Collate to use for lineage resolution. Set this to the service you created with the Data 360 database connector so pipeline lineage can link to the right tables. * **Service Mapping**: A JSON object mapping a Data 360 connector or data source name to the Collate service that holds it, used to resolve the upstream table of a Data Stream. For example: `{"S3_Connector": "my-s3-service"}`. Defaults to `{}`. * **Pagination Limit**: How many Data 360 objects to request per page when listing pipeline objects. Defaults to `10`. Valid values are `1`–`200`. * **Include Bulk Lineage**: When enabled, Collate also ingests lineage from Data Lake Objects to Data Model Objects for every data space. This walks all Data Model Objects in the configured Data 360 database service, so it is off by default. * **Consumer Key**: The consumer key from your Salesforce connected app. This is the client identifier used for OAuth authentication. * **Consumer Secret**: The consumer secret from your Salesforce connected app. This is the client secret used for OAuth authentication. #### Test Connection 1. Click **Test Connection** to verify the credentials. 2. After the test succeeds, click **Save**. Test Connection ### Step 5: Configure Ingestion Options In the **What to Ingest** step, use filter rules to control which pipelines Collate ingests from Salesforce Data 360. #### How Filter Rules Work Each rule matches pipeline names using one of five match types: * **contains**: matches any name containing the value. For example, `sales` matches `my_sales_data` and `sales_2024`. * **starts with**: matches names beginning with the value. For example, `prod_` matches `prod_db` and `prod_schema`. * **ends with**: matches names ending with the value. For example, `_raw` matches `events_raw` and `logs_raw`. * **is exactly**: matches the exact name only. For example, `analytics` matches only `analytics`. * **matches regex**: matches names using a regular expression. For example, `^prod_.*_v\d+$` matches `prod_events_v1`. When include and exclusion rules both match a pipeline, the exclusion rule takes priority. **Tip**: Leave all filter rules empty to ingest all pipelines available in the source. #### Filter Options The **Pipeline** section controls which pipelines Collate ingests from Salesforce Data 360. It provides the following controls: * **Scan Mode**: Choose between the following scan modes: * **Scan all**: Ingests every pipeline the connector can access. This is the default. * **Only specific**: Enables include rules so only pipelines matching at least one rule are ingested. * **Always exclude**: Add permanent exclusion rules (shown in red). Pipelines matching these rules are never ingested, regardless of include rules. * **Preview**: Shows a real-time summary of what will be in scope based on your current rules. * **Include rules**: In **Only specific** mode, click **+ Add** to define a rule. Added rules appear as chips. A pipeline is included if it matches any rule. ### Step 6: Create & Deploy Click **Create & Deploy** to deploy the agent and start the first metadata ingestion run. Collate saves the service configuration and immediately begins pulling metadata from the source. To monitor ingestion progress or view the service you just added, go to **Settings** > **Services** and select your service. ## Configure Metadata Agent and Schedule Ingestion The **Metadata Agent** extracts pipelines, tasks, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click **Create & Deploy**, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the **Agents** tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps: 1. Navigate to **Settings** > **Services** and select the **Pipelines** service. 2. Select your service and click the **Agents** tab. 3. Click **Add Agent** and select **Metadata** from the dropdown. Add Metadata Agent For some services, the dropdown is not available and clicking **Add Agent** takes you directly to the agent configuration page. 4. On the **Configure Ingestion** page, do the following and click **Next**. * **Name this Ingestion**: Enter a unique, recognizable name for this ingestion pipeline. Name this Ingestion * **Agent Setup**: Configure the core parameters for this agent. The following fields are available: | Field | Default | Description | | - | - | - | | Ownership Update Mode | replace | Set how owners from source metadata update Pipeline owners. In replace mode, resolved owners from the current source replace existing owners. In append mode, resolved owners are appended to active existing Pipeline owners. | | Db Service Names | — | List of database service names used for lineage resolution. | | Storage Service Names | — | List of storage service names used for lineage resolution. | | Messaging Service Names | — | List of messaging service names used for lineage resolution. | | Status Lookback Days | 1 | Number of days of pipeline run status history to ingest. Only runs within the last N days will be fetched. | | Include Lineage | On | Turn off to stop fetching lineage from pipelines. | | Mark Deleted Pipeline | On | Soft-delete pipelines in Collate when they are removed from the source. Associated entities like lineage are also deleted. | | Include UnDeployed Pipelines | On | Toggle whether un-deployed pipelines should be ingested. If set to false, only deployed pipelines will be ingested. | Agent Setup * **Filter Patterns**: Apply include or exclude rules to scope which pipelines this agent ingests. These follow the same filter options described in **Step 5**. Filter Patterns * **Scope & Behaviour**: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs: | Toggle | Default | Description | | - | - | - | | Enable Debug Log | Off | Sets the ingestion log level to DEBUG. Useful for troubleshooting. | | Override Metadata | Off | When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. A description or display name that the source doesn't send never replaces an existing value. When off, Collate only updates fields that have no existing value. | | Override Lineage | Off | When on, existing lineage is replaced with newly extracted lineage on each run. | Scope & Behaviour 5. On the **Schedule Interval** page, set when the agent runs: * **Schedule**: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression. * **On-Demand**: No automatic schedule. Trigger the agent manually when needed. Schedule Interval 6. Click **Add** to deploy the agent. ## Configure the Lineage Agent The Metadata agent does not ingest lineage. After the Metadata agent succeeds, add a separate Lineage agent: 1. Open the pipeline service and select the **Agents** tab. 2. Click **Add Agent**, then select **Add Lineage Agent**. 3. Configure its schedule. 4. Click **Add & Deploy**. The Lineage agent requires **Data 360 Database Service Name** in the service connection. The workflow fails when that field is empty. **Include Bulk Lineage** also applies only to the Lineage agent. Enable it to ingest Data Lake Object-to-Data Model Object lineage for every data space. ## Configure the Usage Agent for Pipeline Status The Metadata agent does not ingest run status. Add a separate Usage agent to populate Pipeline Status: 1. Open the pipeline service and select the **Agents** tab. 2. Click **Add Agent**, then select **Add Usage Agent**. 3. Set **Status Lookback Days** to the run-history window you want to ingest. 4. Configure its schedule. 5. Click **Add & Deploy**. ## Troubleshooting Learn more about how to troubleshoot common Salesforce Data 360 pipeline connector issues and resolve configuration or ingestion errors. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.