Salesforce Credentials

Overview

Salesforce credentials that sign in with username, password and security token stop working when Salesforce retires SOAP login() with the Summer '27 release (June 2027). DataBlend's October 2026 1.0 Major release (shipped October 12, 2026) lets an OAuth credential run your existing collectors and data targets over the SOAP API, so you can move off the old login without changing your output.

Username/password credentials keep working until Salesforce turns off login(). Nothing changes for a collector or data target until someone edits it.

What this means for you

Every Salesforce collector and data target that uses a username/password credential must be re-pointed to an OAuth credential before June 2027. The combination of credential type and the toggle decides how DataBlend talks to Salesforce:

Workflows, schedules and downstream queries keep working as long as the collector's output columns stay the same. Choosing OAuth + SOAP is the safest way to guarantee that.

How to transition

The move takes three parts: a Salesforce admin sets up the app once, you create one OAuth credential, then you re-point each collector and data target.

Part 1: Salesforce admin (once per org)

Part 2: Create the REST credential in DataBlend

Part 3: Re-point each collector and data target

Salesforce Login Types:

Standard/SOAP (Credentials) - retiring June 2027

REST API (OAuth) - recommended for all new connections

Connect Using Credentials (Standard/SOAP)

Troubleshooting SOAP API connection:

This will likely be a necessary first step for anyone new to Salesforce. Salesforce removes this option with the Summer '27 release (June 2027). Use a REST API credential instead of setting up a new Standard/SOAP credential.

1. Switch to the Classic UI in Salesforce (top right corner under your user area).
2. After your display reloads, click Setup in the top right corner to get to the admin area
3. In the Quick Find box in the top left, type "User Interface"
4. 2/3 down that list of options is the "Enable SOAP API login()" option.  
5. Check the radio button
6. Scroll to the bottom and click Save.

At this point, you can switch back to the Lightning UI and the security token login should work.   

Note: If the option's checkbox is greyed out, Salesforce has already turned off SOAP login for your org. Connect using the REST API instead.

Connect using REST API

The REST API can be used to access objects that may not appear in the standard connection. DataBlend can establish a connection with any Salesforce Edition that supports API access:

• Enterprise Edition
• Unlimited Edition
• Developer Edition
• Performance Edition
• Professional Edition, however, the optional Web Services API add-on must be purchased and can be processed through an Account Executive

To establish a connection with Salesforce in DataBlend with REST API, first create DataBlend as an External Client App in Salesforce (a Salesforce admin does this once per org):

1. Log into Salesforce and click on the gear icon to navigate to Setup.
2. Search for "External Client App Manager" or navigate under the PLATFORM TOOLS section to expand "External Client Apps" and click on "External Client App Manager".
3. On the upper-right, click on the "New External Client App" button and refer to Configure Basic Connected App Settings while completing the Basic Information section.
4. See Enable OAuth Settings for API Integration for how to set up DataBlend as an app:
   1. Under the API (Enable OAuth Settings) section, be sure to checkmark "Enable Auth".
   2. The Callback URL is https://ml.datablend.com/api/plugins/salesforce/oauth.
      
      1. Under Selected OAuth Scopes, add the scopes "Manage user data via APIs (api)" and "Perform requests at any time (refresh_token, offline_access)".
   3. 
   4.  Verify appropriate scopes are enabled in Salesforce by referring to OAuth Tokens and Scopes.
      
   5.  Under Flow Engagement, checkmark the following.
      
   6. Under Security, checkmark Require Proof Key for Code Exchange (PKCE) extension for Supported Authorization Flows.
5. Click the Create button.
6. When you understand the security risks, accept the warning.
7. Select an execution user for the flow.
   Although there’s no user interaction in the client credentials flow, Salesforce still requires you to specify an execution user. By selecting an execution user, you allow Salesforce to return access tokens on behalf of this user.
   Note Permitted Users policies, such as All users may self-authorize and Admin approved users are pre-authorized, don’t apply to the execution user  
   1. From the connected app detail page, click Manage.
   2. Click Edit Policies.
   3. Checkmark "Enable Client Credentials Flow" under OAuth Flows and External Client App Enhancements and enter a username (found in View Profile > Personal Information). Click save. For Enterprise Edition orgs, we recommend that you select an execution user who has the API Only User permission.
   4. Save your changes.

8. In the PLATFORM TOOLS SECTION, expand "External Client Apps" to navigate to “Settings” and toggle on "Allow access to External Client App consumer secrets via REST API". Also check the "OAuth Usage" page.

After Connection is established, create the REST credential in DataBlend.

1. Create a new Salesforce credential.
2. Toggle ON "Use REST API".
3. Select an Environment plus enter the Client ID and Client Secret.
4. Click Save.
5. Click Connect.
6. Click authorize and sign in to Salesforce when prompted. DataBlend stores the tokens and refreshes them automatically.
7. Test the credential.