Set up credentials
You create an OAuth app in Salesforce Setup, then copy its consumer key and consumer secret. As of the Spring ‘26 release, Salesforce recommends External Client Apps over Connected Apps, and creating new Connected Apps may require contacting Salesforce Support.1
Open Setup
Log in to your Salesforce org. Click the gear icon and select Setup.
2
Open App Manager
In the Quick Find box, type
App Manager and select App Manager.3
Create a new app
Click New Connected App. If prompted, choose to create an External
Client App instead, which is the option Salesforce now recommends. Enter a
Connected App Name, API Name, and Contact Email.
4
Enable OAuth settings
Select Enable OAuth Settings. Enter a Callback URL (for example,
https://login.salesforce.com/services/oauth2/callback) and add the OAuth
scopes your integration needs, such as Manage user data via APIs (api)
and Perform requests at any time (refresh_token, offline_access). Click
Save.5
Copy the consumer key and secret
After saving, open the app and go to Manage Consumer Details (you may be
asked to verify your identity). Copy the Consumer Key and Consumer
Secret. Allow a few minutes for the new app to activate before using it.
In Lightning Experience you can find the app again later under Setup > App
Manager. Use the row dropdown and select View, then Manage Consumer
Details to retrieve the key and secret.
Connect to Adapt
1
Open Integrations
In Adapt, go to Settings > Integrations.
2
Find Salesforce
Search for Salesforce and select it from the catalog.
3
Start the connection
Click Connect to open the connection form.
4
Add your credentials
Enter the values you gathered above, then click Add connection:
You can rename the connection and choose whether it is shared with your
organization or kept personal to you.
5
Test the connection
Ask Adapt to list your most recent opportunities.
Security
- Credentials are encrypted at rest with AES-256
- Grant only the OAuth scopes your use case needs, such as
apiandrefresh_token - Use a dedicated integration user with least-privilege access where possible
- Never share the consumer key or secret publicly or commit them to source control