Salesforce Output Connection

Note

As of Summer '27, the SOAP API login() call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available. For more information, see SOAP API login() Call in SOAP API Versions 31.0 Through 64.0 Is Being Retired.

The Username and Password authentication settings in external connectors will no longer be supported starting in Winter '27.

New external connectors require OAuth with Client ID and Client Secret for authentication. Existing connectors using Username and Password can still function if the SOAP API login() is enabled in your org permissions. However, if you need to update the credentials for an existing Username and Password connector, you must convert it to use OAuth settings.

Restricted API access isn't supported for Salesforce Output and External connectors. Enable the Use Any API Client permission for the user creating the connector. For more information, see Manage API Access.

Use the Salesforce External Connections to sync data from another Salesforce org to Salesforce Data Pipelines.

How the Salesforce Output Connector with Output Node Works

The Salesforce Data Pipelines Salesforce Output connectors allow you to write the outcome of a recipe to any Salesforce org for further analysis, business automation, and expanded access. After you configure an output connector to the Salesforce org, create a recipe using Data Prep. Add an Output node to the recipe, select the Salesforce Output connection, and configure the node with the object, mapping, and other settings. When the recipe runs, Salesforce Data Pipelines can INSERT, UPDATE, or UPSERT the output dataset to supported objects.

Set Up an External Client App for OAuth

External client apps (ECA) provide single sign-on (SSO) and use OAuth protocols to authorize external connections.

Note

It’s recommended to create a separate Salesforce user account that isn’t assigned to a person to set up a connection. A person’s account can be deactivated when the user leaves your organization, which stops any connections created with the account from functioning.

1. To create an ECA for your ‌organization, from the Salesforce Setup page, enter External in the Quick Find box, and then select External Client App Manager.
2. Click New External Client App.
3. Enter the basic information.
   1. Enter the name for the ECA to display in the External Client App Manager.
   2. Enter the API name to be used when referring to your app from a program. This field defaults to a version of the app’s name with underscores in place of the spaces.
   3. Enter the contact email for Salesforce to use in case we want to contact you or your support team.
   4. Select Local for the Distribution State.
4. Click Enable OAuth to configure the OAuth policy.
5. Enter the app settings.
   1. Enter the Callback URL. The callback URL is the app URL where you’re embedding the code and the URL can accept the authentication returned from the Salesforce ECA. An example of a callback URL is https://<3p-domain>/callback.html.
   2. For OAUTH Scopes, select Manage user data via APIS (api) and Access Analytics REST API resources (wave_api). If you have other OAuth needs, select other scopes as needed. For more information, see OAuth Tokens and Scopes
6. For Flow Enablement, select Enable Client Credentials Flow. This flow allows for server to server interactions. For more information, see OAuth 2.0 Client Credentials Flow for Server-to-Server Integration
7. For Security, disable Require Proof Key for Code Exchange (PKCE) extension for Supported Authorization Flows.
8. Click Create.
9. On the Policies tab, click Edit. For OAuth Flows and External Client App Enhancements, ensure Enable Client Credentials Flow is enabled. Enter a user email for Run As. This user must be a valid execution user.
10. On the Settings tab, click Consumer Key and Secret to copy and save the values. You need the consumer key value for the Client Id and the consumer secret value for the Client Secret.

Enable and Add the Salesforce Output Connector

1. From Setup, in the Quick Find box, enter Analytics, select Analytics, and then Settings.
2. Select Enable Salesforce output connection and then save your changes.
3. In the Data Manager, click the Connections tab.
4. Click New Connection.
5. Click Output.
6. Select Salesforce Output Connector.
7. Enter the connection settings.
8. Click Save & Test. Save & Test validates your settings by attempting to connect to the source. If the connection fails, Salesforce Data Pipelines shows possible reasons.

All settings require a value, unless otherwise indicated.

https://mycompany.my.salesforce.com/services/Soap/u/34.0

Push Data to Salesforce

With the Salesforce Output Connector configured, build a Data Prep recipe that merges and transforms the data to push to a Salesforce org. Add an output node and configure it to use the Salesforce Output connector.

1. Select to write to an Output Connection (1).
2. Select the connection name of the Salesforce Output connection you created (2).
3. Select the destination Salesforce object (3). Objects available to the User ID used to configure the connector are listed. Supported objects are listed in Considerations.
4. Choose whether to INSERT (add new records), UPDATE (change data of existing records), or UPSERT (add new records and update existing records). (4)
5. If you UPSERT, select a field from the destination object for the External ID to act as the unique record identifier. (5) The default External ID is the connected object’s ID field.
6. Map recipe columns to their equivalent Salesforce object columns. (6) All columns must be mapped to apply the output node. Id is only mapped for UPDATE and UPSERT.
7. Select Apply.
8. Save the recipe.

Salesforce Output Connector Considerations

Keep these behaviors in mind when working with the Salesforce output connector and using a Data Prep recipe output node.

• To troubleshoot unsuccessful or partial failed runs, see Investigate Unsuccessful Salesforce Output Connector Runs.
• You can use an output connection more than once per recipe, but each output node must use a different object. Each output node can use up to the connector's per-run limit independently, but is still subject to the rolling 24-hour limit.
• Output connections are only available for recipes built with Data Prep.
• This connector doesn’t support objects that are the parent or child in a parent-child relationship. If there are two custom objects with a dependency, manually insert the header record, get the header ID, then insert the detail record with those details.
• Sharing descriptors, the ID of any user or group that has access to a record, aren’t included in the output from the source org to the target org.
• This connector supports INSERT, UPDATE, and UPSERT to:
  • Custom objects
  • Salesforce objects:
    • Account
    • AccountContactRelationship
    • AccountForecast
    • AccountProductForecast
    • AccountProductPeriodForecast
    • AccountForecastPeriodMetrics
    • AccountTeamMember
    • Activities
    • AdvAccountForecastFact
    • AdvAccountForecastSetPartner
    • Asset
    • Campaign
    • CampaignMember
    • Cases
    • ContactPointAddress
    • ContactPointEmail
    • ContactPointPhone
    • Contacts
    • CurrencyType
    • Event
    • Leads
    • ObjectTerritory2Association
    • Opportunity
    • OpportunityLineItem
    • OpportunityLineItemSchedule
    • OpportunityTeamMember
    • Order
    • OrderItem
    • Product2
    • ProgramRebateTypPayoutSrc
    • RebateMemberProductAggregate
    • RebateProgramMemberPayout
    • RebateProgramPayoutPeriod
    • Task
    • TransactionJournal
  • Salesforce Industries objects:
    • AccountServicePreference (Health Cloud)
    • Claim (Automotive Cloud, Financial Services Cloud, and Manufacturing Cloud)
    • ClaimItem (Automotive Cloud, Financial Services Cloud, and Manufacturing Cloud)
    • QuoteLineItem (Commerce Cloud)
    • SalesAgreement (Manufacturing Cloud)
    • Visit (Consumer Goods Cloud)
• To output null measure values to Salesforce, see Enable Null Measure Handling. To output null dimension values, add a bucket transformation for each dimension column with nulls, select Bucket null values, and set the value N/A.