Skip to main content
Ensure you have Admin privileges for your Salesforce account.

Creating a Connected App

To connect Salesforce with StackOne, you need to create a Connected App in your Salesforce org to obtain OAuth credentials.

1

Sign in to Salesforce Setup

Sign in to your Salesforce account and click the Setup ⚙️ icon in the top-right menu.

2

Navigate to App Manager

In the left navigation under Platform Tools, expand Apps and click App Manager.

  • Click the New External Client App button in the top-right corner
3

Enter Application Information

In the Basic Information section, enter the following details.

  • External Client App Name: StackOne Integration (or your preferred name)
  • API Name: Will auto-populate based on the app name
  • Contact Email: Your admin email address
  • Leave Distribution State set to Local.

Configure OAuth Settings

Enable and configure OAuth settings for API access.

1

Enable OAuth Settings

Check the Enable OAuth Settings checkbox to expand the OAuth configuration section.

  • In Callback URL, enter: https://api.stackone.com/connect/oauth2/salesforce/callback
2

Select OAuth Scopes

Under Selected OAuth Scopes, add the following scopes.

  • Manage user data via APIs (api)
  • Perform requests at any time (refresh_token, offline_access)
3

Configure Security Settings

In the Security section, set the following. Salesforce always turns on PKCE and refresh token rotation for apps created on or after 9 July 2026, and StackOne supports both.

  • Keep Require secret for Web Server Flow and Require secret for Refresh Token Flow checked
  • Keep Require Proof Key for Code Exchange (PKCE) extension for Supported Authorization Flows checked
  • Enable Refresh Token Rotation can stay checked
4

Save the Connected App

Click Create at the bottom of the page.

  • You will be redirected to the Connected App detail page
  • Note: It may take up to 10-20 minutes for the app to become active

Retrieve Consumer Credentials

Obtain the Client ID and Client Secret for StackOne configuration.

1

Access Consumer Details

In the left navigation under Platform Tools, expand Apps then External Client Apps and click External Client App Manager or OAuth Usage.

  • Open the app you created (e.g., StackOne Integration)
  • Go to Settings > OAuth Settings
  • Click Consumer Key and Secret
  • You may be prompted to verify your identity via email or authenticator
2

Copy Credentials

Copy the Consumer Key (Client ID) and Consumer Secret (Client Secret).

  • Store these credentials securely for use later
  • The Consumer Key is your Client ID
  • The Consumer Secret is your Client Secret

Approve Access When Connecting

The first time someone connects, Salesforce may show an Allow Access? screen for your app, with a security warning about apps you were told to use. This is your own app, so click Allow. Clicking Deny stops the connection with the error end-user denied authorization.

1

If Allow Access does not appear or the connection fails

Check the app policy and the sign-in history in Salesforce.

  • In External Client App Manager, open your app and go to its Policies tab
  • Check Permitted Users. With Admin approved users are pre-authorized, add the profile or permission set of every user who will connect.
  • In Setup, open Login History to see whether the sign-in was blocked

Selecting an Environment

Both environments sign in through login.salesforce.com, so they connect the same way.

1

Choose Your Environment

Choose the environment for your Salesforce org.

  • Production: your live org, plus Developer Edition and trial orgs
  • Sandbox: sandbox orgs can’t connect yet, because sign-in always goes through login.salesforce.com

Custom OAuth Scopes

If you need to customize the OAuth scopes, keep the following in mind.

1

Refresh Token Scope

StackOne always requests refresh_token, so the connection stays signed in even when you enter your own scope list.

  • If the OAuth Scopes field is left blank, the default scopes (api refresh_token offline_access) are used automatically
  • If you specify custom scopes, you do not need to type refresh_token (e.g., api chatter_api content)
  • The Connected App must still have Perform requests at any time selected under Selected OAuth Scopes
  • Every custom scope you specify must also be added to the Connected App’s Selected OAuth Scopes, otherwise Salesforce returns an OAuth Error

Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Salesforce:
1

Open the connector

Log in to StackOne, open Connectors, and select Salesforce.
2

Choose actions and events

  • Click Add Profile.
  • If the connector offers more than one authentication method, set the Auth Method filter to OAuth 2.0.
  • Select the actions, and any events, to enable for this Connector Profile.
  • Click Continue.
3

Set up authentication

  • Select Authentication Type as OAuth 2.0.
  • Fill out the fields using details retrieved from your provider:
    • Client ID (Consumer Key)
    • Client Secret (Consumer Secret)
    • OAuth Scopes (Optional)
  • Click Create Profile.
Congratulations! The new Connector Profile now shows up on the connector page. If you created it as a project member rather than an admin, it starts disabled until a project admin enables it. You can now continue to Link Accounts for Salesforce.