2. Click **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.
### Step 3: Add Service Name and Description
1. Enter a unique, descriptive **Service Name**. OpenMetadata identifies services by their service name. Enter a name that distinguishes this deployment from other Salesforce Data 360 services you are ingesting metadata from.
2. Optional: Enter a **Description** for the service.
* **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 OpenMetadata 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 OpenMetadata 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, OpenMetadata 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's 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
After you add the credentials, click **Test Connection**, then click **Save**.
### Step 5: Configure Ingestion Options
In the **What to Ingest** step, configure filter rules for pipelines.
#### 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 rules and exclude rules both match a pipeline, the exclude rule takes priority.
2. Click the service you have added.
3. Select the **Agents** tab and click **Add Agent** > **Metadata**.
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.
* **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 OpenMetadata 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. |
* **Filter Patterns**: Apply include or exclude rules to scope which pipelines this agent ingests. These follow the same filter options described in **Step 5: Configure Ingestion Options**.
* **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 OpenMetadata. When off, OpenMetadata only updates fields that have no existing value. |
| Override Lineage | Off | When on, existing lineage is replaced with newly extracted lineage on each run. |
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.
6. Click **Add** to deploy the agent.
## Configure the Lineage Agent
The Metadata agent doesn't 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 doesn't 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**.
## Related