---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up the Salesforce spoke

# Set up the Salesforce spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 12 minutes to read  
Integrate your Salesforce account with your ServiceNow instance. Create a custom OAuth
application in Salesforce and authenticate requests from ServiceNow.

## Before you begin

* Request an Integration Hub subscription
* Activate the Salesforce spoke
* Role required: admin.

{#setup-sf-spk__ul_m44_zrb_xrb}  
Note:  
Two spoke setup procedures are outlined here. Perform one of the procedures as per your requirement.

* To setup the spoke using OAuth authorization template, see [Option 1: Set up the Salesforce spoke using OAuth authorization template](https://www.servicenow.com/docs/ec3tP~pivVnLI2BcUrStjQ#setup-sfspk-template "Integrate your Salesforce account with your ServiceNow instance. Create a custom OAuth application in Salesforce and authenticate requests from ServiceNow using OAuth authorization template.").
* To setup the spoke using JWT signing key, see [Option 2: Set up the Salesforce spoke using JWT signing key](https://www.servicenow.com/docs/ec3tP~pivVnLI2BcUrStjQ#setup-salesforce "Integrate your Salesforce account with your ServiceNow instance. Create a custom OAuth application in Salesforce and authenticate requests from ServiceNow using JWT signing key.").
{#setup-sf-spk__ul_m4r_ctb_xrb}  
Note:  
Don't delete the default connection alias record. This can result in an unexpected behavior. Configure your connection using the default connection alias.

## Configure a connection for Salesforce spoke {#ariaid-title2}

Add and configure a Salesforce connection to authenticate ServiceNow requests in Salesforce spoke.

### Before you begin

Role required: admin

### Procedure

1. Navigate to Process AutomationWorkflow Studio.
2. Select Integrations.
3. Select the Connections tab.
4. Use the search box to find the Salesforce connection alias.
5. Select View Details.
6. Configure the Salesforce connection.
   1. Add or edit a connection.  
      * To set up an existing connection, select Configure or Edit.
      * To create and configure a new connection, select Add Connection.

      {#config-connection-salesforce-spoke__ul_salesforce_add_edit}  
      Note:  
      To support multiple connections through a spoke, see [Supporting multiple connections](https://www.servicenow.com/docs/D9pGgVwvfvFrzWX3lknyWg "Support several connections to a single integration provider. Select connections for flows, subflows, and actions directly from a flow.").
   2. On the configuration form, fill in the fields.  
      {#config-connection-salesforce-spoke__table_salesforce_conn_config__entry__2}

      | Field | Description |
      |-|-|
      | Connection Name | Name to uniquely identify the connection. For example, <kbd class="ph userinput">Salesforce</kbd>. |
      | Connection URL (Instance URL) | URL to make a connection to Salesforce. Use this format: <kbd class="ph userinput">https://&lt;organization_name&gt;.my.salesforce.com</kbd>. |
      | Grant Type | OAuth grant type for authentication. Select one of the following options: * Authorization Code * Client Credentials {#config-connection-salesforce-spoke__ul_grant_type_options} |
      | OAuth Client ID | Client ID generated in Salesforce for OAuth authentication. |
      | OAuth Client Secret | Client Secret generated in Salesforce for OAuth authentication. |
      | OAuth Redirect URL | URL where Salesforce redirects after successful authentication. Use this format: <kbd class="ph userinput">https://&lt;instance_name&gt;.service-now.com/oauth_redirect.do</kbd>. |
      [ ]

      {#config-connection-salesforce-spoke__table_salesforce_conn_config}
   3. Select Save and Get OAuth Token.
   {#config-connection-salesforce-spoke__substeps_salesforce_conn}
{#config-connection-salesforce-spoke__steps_salesforce_config}

### Result

The Salesforce spoke connection is configured and ready to be used.

## Create a connected app in Salesforce {#ariaid-title3}

Create a connected app in your Salesforce account to enable OAuth 2.0 authentication with the Salesforce spoke.

### Before you begin

* Salesforce account
* Role required: Salesforce admin
{#create-connected-app-sf__ul_wwy_j1v_g3b}

### About this task

Complete these steps from your Salesforce account. See [Create a Connected App](https://help.salesforce.com/articleView?id=connected_app_create.htm&type=5) in [Salesforce Trailblazer forum](https://success.salesforce.com/) documentation for instructions on creating and configuring connected apps.

### Procedure

1. From your Salesforce account, create a connected app.
2. Configure the connected app to enable your Salesforce application to share data with your ServiceNow instance.
   1. Select Enable OAuth Settings and configure the authentication settings.
   2. If you want to set up the spoke using JWT signing key, select Use Digital Signatures and upload a Java KeyStore (JKS) certificate.
   3. Select the OAuth scopes:  
      {#create-connected-app-sf__table_bpb_n2q_yhc__entry__2}

      | Grant Type | OAuth scopes |
      |-|-|
      | Authorization Code | * Access and manage your data (api) * Perform requests on your behalf at any time (refresh_token, offline_access) {#create-connected-app-sf__ul_mbh_2dv_g3b} |
      | Client Credentials | Access and manage your data (api) |
      [ ]

      {#create-connected-app-sf__table_bpb_n2q_yhc}
   4. Specify ServiceNow instance URL in Callback URL in this format: <kbd class="ph userinput">https://&lt;instance-name&gt;.service-now.com/oauth_redirect.do</kbd>
   5. After creating the connected app, under OAuth Policies on the Edit Policies page, set these values:  
      {#create-connected-app-sf__table_y4h_w45_fnb__entry__2}

      | Field | Value |
      |-|-|
      | Permitted Users | Admin approved users are pre-authorized |
      | IP Restrictions | Relax IP Restrictions |
      [ ]

      {#create-connected-app-sf__table_y4h_w45_fnb}
   6. Configure user provisioning for the connected app as per your requirement.
   {#create-connected-app-sf__substeps_npt_fcv_g3b}
3. Record the values of Consumer Key and Consumer Secret.  
   Note:  
   * Assign profile and permission set as per your requirement.
   * In OAuth app IP restrictions, specify OAuth policies to ensure that the connected app works like a default app.
   {#create-connected-app-sf__ul_jc2_svb_xrb}
{#create-connected-app-sf__steps_zp5_l45_fnb}

### Result

The connected app is created in Salesforce.

## Option 1: Set up the Salesforce spoke using OAuth authorization template {#ariaid-title4}

Integrate your Salesforce account with your ServiceNow instance. Create a custom OAuth application in Salesforce and authenticate requests from ServiceNow using OAuth authorization template.

### Before you begin

* [Create a connected app in Salesforce](https://www.servicenow.com/docs/ec3tP~pivVnLI2BcUrStjQ#create-connected-app-sf "Create a connected app in your Salesforce account to enable OAuth 2.0 authentication with the Salesforce spoke.")
* Role required: admin
{#setup-sfspk-template__ul_nmb_3tb_xrb}

### Procedure

1. Log in to [Salesforce](https://login.salesforce.com/?startURL=/setup/secur/RemoteAccessAuthorizationPage.apexp?source=CAAAAWd_ycj7ME8wMHkwMDAwMDA4T0k2AAAA2CFKH_C6K2jEXMcAAa95DHha0KQ0IeY1ykrwEVRkz67RUi8i4a0jM7Vp8V21BaS_L33r3duBQbWQwqlyiK2ggRW4EpVHap4wptWMLW6rSLEX9sFPr9tx-KL10Co6XYnGi6obC4k1a5vaO0N2nCjm2hZZ9ncAxKjFL7Dg5Yn93smtqoQquTJlPn85UW8f4CtFFRxNmMkvCs8fsBriDWCmolMpA7RSre5FgwDVuhOsLTVi7WcOvYa9KQof9RQDptCwsh3emhXvc0b4eIr_mTHD1q-yCB8LCgtH3PZLh7NlpywhUjvaEcqLC1LIaM-s7zxbvNdJnNiYx7ZBVMgvLc7KuHqTrJqnKEHVqRUAQjDbpNHV7IIsiviaGhEnY1uwJM84XtO2z2NYSjT-ANIriMblKQXaVGMucWCSZjvvT-XzrgEUPQCK6ZloS4-icbOjf7dNOIWxBR_Ps6Ux3mmvZE8wsABMyFuPAa0lJr9JLsS1EYT_LXBJSWGZ8GajEk55_zQzkxZzWRX5H5nkqxXu6xIVqNVUdS6DkiK4SSJ0nkLEFyQ3HoAVdWxegmYkcqVgy0KupBs-i2KSW47vgr6D3dU0pWhPaLkf10V3m1kd_C3ZL6ic8MS4_lUtsoyR7T9NbpRdeQ1gERuDu-tRSVgdcPkVi9Kxn9DUvhuFiQx1Cs8F2tcqE417kbJqONd7_2M1UL9b5Wy3s_T5SD1tbjsi9hwvEK1hfIe-JmxykwGgIZRT5Q4rQ-GlkJWxSiIxZOJrWI5ZoNbZX7_GIcC01InFN8OMveE1EAvO4JuC3KZ8Yxwypmr5jUYqzQLOLWhDB5mjoEwdFbns1PQtgwwkFjRnfEI90yysbVMQwMq2X8rp75vc-KDMrqTWyALTkVDbxsyuMWfLqUZ5NFaHggbtwQO7fK9o3ZESzswI6YBZWnzbEmHYaOPjbSIulXe7XjbLVLEMEXyLyr3V7PAPtGv_t3Y0mEG0NeenO_pi3NfUFxgvTZo571hgbEVqSvEdgtJWzTLYN0VxKIf7iYcJwO_zRRPCEA4vpJqha-ppCesm1EwjzdQPj7g0lh7G4faQ4916YDLiJCH2MFPTzyz4z4ib0Zg4ejnPPt3v7xWDenkSL6SiD8PgYSA7zPiTZSuMbXt0TOVXyIhg-RsVaDx9Nlv1Jz5NdDWXUWsxk_vI6LJv63Ib_Ky-X6yalB2bY-Y5GyuthFOpIgEjv1P-NurpdZkHdfKR3EdxgBzpnl35XW2M_7oyz9M0CK1MbxaYlgS6t0LVKkXJC21oMaMnykekz7coxVVZxg94Y28J_zZ0Hk75Xj4yuwRc04XSWvwhyDvaYGV5cR7zXeimrMmMylEBYQOxr7-UBSzxoSuLIJWuDxW2qaIwwW8s134O1U62SPYe-l6m1vzq3AZ6vlYpkngznqLjS6iVruD2qbw%3D&sdtd=1).  
   You can also switch from the Lightning UI.
2. Select the setup icon ![]() and then select Setup.
3. Search for and select  OAuth and OpenID Connect Settings  in the setup page search bar.
4. Enable Allow Authorization Code and Credentials Flows.
5. Search for and select App Manager in the setup page search bar.
6. On the App Manager page, select New External Client App to create an external client application.
7. On the form, fill in the fields.  
   {#setup-sfspk-template__table_ylm_f1h_1gb__entry__2}

   | Field | Description |
   |-|-|
   | Basic Information ||
   | External Client App Name | Name of your application. |
   | API Name | Name of the API. This field is automatically populated. |
   | Contact Email | The email address that you want to associate with the application. |
   | Distribution State | The scope of distribution of the application. Select Local as the distribution state. |
   | Contact Phone | The phone number that you want to associate with the application. |
   | Info URL | The URL of the web page with more information about your application. |
   | Logo URL | The URL of your logo image that is displayed with the connected application. |
   | Icon URL | The URL of the icon for the connected application. |
   | Description | Description of the application. |
   | API (Enable OAuth Settings) ||
   | Enable OAuth | Option to enable OAuth settings. Select this option to enable the OAuth settings. |
   | Callback URL | URL of the OAuth provider that users are redirected to after authentication. Enter <kbd class="ph userinput">https://<var class="keyword varname">instance</var>.service-now.com/oauth_redirect.do</kbd>, where \<<var class="keyword varname">instance</var>\> is the name of your ServiceNow instance. |
   | OAuth Scopes | OAuth scopes that determine the amount of access that is granted to an access token. When the grant type is Authorization Code, use: * Manage user data via APIs (api) * Perform requests at any time (refresh_token, offline_access) {#setup-sfspk-template__ul_t1z_1vy_dgc} When the grant type is Client Credentials, use Manage user data via APIs (api). |
   | Flow Enablement ||
   | Enable Client Credentials Flow | Select this option when the grant type is Client Credentials. |
   | Security ||
   | Require Secret for Web Server Flow | The option to implement the Require Secret for Web Server Flow in your external client app or connected app settings. * If the grant type is Authorization Code, select this option. * If the grant type is Client Credentials, clear this option. {#setup-sfspk-template__ul_knh_jmg_shc} |
   | Require Secret for Refresh Token Flow | The option in your external client app or connected app while implementing the refresh token flow using a server-side callback handler. * If the grant type is Authorization Code, select this option. * If the grant type is Client Credentials, clear this option. {#setup-sfspk-template__ul_ybt_mmg_shc} |
   | Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows | If this field is selected by default, clear the Require Secret for Web Server Flow and Require Secret for Refresh Token Flow options. Note: Enable Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows. |
   [ ]

   {#setup-sfspk-template__table_ylm_f1h_1gb}
8. Select Create.  
   The application registration is complete and you're redirected to the Manage External Client Apps page.
9. Verify and edit the policies for the registered application by selecting Edit.
10. In the OAuth Policies section, verify that the Permitted Users field is set to Admin approved users are pre-authorized for the ServiceNow application.  
    Note:  
    Admin-approved users who are preauthorized enable any users with the corresponding profile or permission set to access the application without prior authorization. For more information, see [Pre-Authorize User App Access Through Connected App Policies](https://help.salesforce.com/s/articleView?id=xcloud.branded_apps_allow_deny_con_app.htm&type=5).
11. In the App Policies section, select either the profile of the integration user or the profile of the user that you want to use for the integration.
12. If you have selected the Enable Client Credentials Flow option, then in the OAuth Flows and External Client App Enhancements section, select Enable Client Credentials Flow and enter either the username or email address of the integration user that you want to use for the integration profile.
13. In the App Authorization section, verify that the Refresh token policy field is set to Refresh token is valid until revoked and the IP Relaxation field is set to Relax IP restrictions.
14. Select Save.
15. Retrieve OAuth credentials.
    1. Navigate to SettingsOAuth Settings and then select Consumer Key and Secret.  
       The Salesforce login page opens in a new window.
    2. Enter your credentials to log in to Salesforce.
    3. Copy the Consumer Key and Consumer Secret and save them in a secure location for later use.
    {#setup-sfspk-template__substeps_n3z_hqp_y2c}
{#setup-sfspk-template__steps_axy_u9bf_h4x}

## Option 2: Set up
the
Salesforce spoke using JWT signing key {#ariaid-title5}

Integrate your Salesforce account with your ServiceNow instance. Create a custom OAuth
application in Salesforce and authenticate requests from ServiceNow using JWT signing
key.

### Before you begin

* [Create a connected app in Salesforce](https://www.servicenow.com/docs/ec3tP~pivVnLI2BcUrStjQ#create-connected-app-sf "Create a connected app in your Salesforce account to enable OAuth 2.0 authentication with the Salesforce spoke.")
* Role required: admin
{#setup-salesforce__ul_lb1_zv5_g3b}

### Attach a Java Key Store certificate to the Salesforce spoke {#ariaid-title6}

Enable the
JSON Web Token
(JWT)
Bearer Grant token authentication by attaching a valid Java KeyStore (JKS) certificate to
the Salesforce spoke.

#### Before you begin

* Valid Java KeyStore certificate
* Role required: admin
{#attach-jks-salesforce__ul_llq_clv_g3b}

#### Procedure

1. Navigate to AllSystem DefinitionCertificates.
2. Click New.
3. On the form, fill in the fields.  
   {#attach-jks-salesforce__table_hvh_4tt_xgb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to uniquely identify the record. For example, <kbd class="ph userinput">Salesforce Certificate</kbd>. |
   | Expiration notification | Option to send a notification when the certificate is about to expire. |
   | Notify on expiration | Users that are notified when the certificate expires. |
   | Warn in days to expire | Number of days to send a notification before the certificate expires. |
   | Active | Option to actively use the certificate. |
   | Format | Certificate format. The instance supports the PEM and DER formats. |
   | Type | Type of certificate. Select Java Key Store. |
   | Valid from | Date from which the certificate is valid. |
   | Expires | Date on which the certificate expires. |
   | Expires in days | Number of days until the certificate expires. |
   | Key store password | Password associated with the certificate. |
   | Short description | Summary about the certificate. |
   | PEM Certificate | Contents of the X509 certificate. |
   [Table 1. X.509 Certificate form]

   {#attach-jks-salesforce__table_hvh_4tt_xgb}
4. Click the attachments icon (![Attachments icon]()) and attach a JKS certificate.
5. Click Validate Stores/Certificates.

#### Result

The JKS certificate is created and attached to the Salesforce spoke.

### Create a JWT signing key for the Salesforce spoke {#ariaid-title7}

Create a JSON Web Token (JWT) signing key to assign to your Java KeyStore
certificate.

#### Before you begin

Role required: admin

#### Procedure

1. Navigate to AllSystem OAuthJWT Keys.
2. Click New.
3. On the form, fill in the fields.  
   {#create-jwtkey-salesforce__table_jky_dk5_xgb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to uniquely identify the JWT signing key. For example, <kbd class="ph userinput">Salesforce JWT Keys</kbd>. |
   | Signing Keystore | Valid JKS certificate attached in the previous task. For example, <kbd class="ph userinput">Salesforce Certificate</kbd>. |
   | Key Id | Key ID to identify which key is used when multiple keys are used to sign tokens. |
   | Application | Application scope that contains this record. Select Salesforce spoke. |
   | Signing Algorithm | Algorithm to sign with the JWT key. |
   | Signing Key Password | Password associated with the signing key. |
   | Active | Option to actively use the certificate. |
   [Table 2. JWT Keys form]

   {#create-jwtkey-salesforce__table_jky_dk5_xgb}
4. Click Submit.

#### Result

The JWT key is created and assigned to the JKS certificate.

### Create a JWT provider for the Salesforce spoke {#ariaid-title8}

Add a JSON Web Token (JWT) provider to your ServiceNow
instance.

#### Before you begin

Role required: admin

#### Procedure

1. Navigate to AllSystem OAuthJWT Providers.
2. Click New.
3. On the form, fill in the fields.  
   {#create-jwtprovdr-salesforce__table_jpx_g4v_g3b__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to uniquely identify the JWT provider. For example, <kbd class="ph userinput">Salesforce JWT Provider</kbd>. |
   | Expiry Interval (sec) | Number, in seconds, to set the lifespan of JWT provider tokens. |
   | Signing Configuration | JWT signing key from the previous step. For example, <kbd class="ph userinput">Salesforce JWT Keys</kbd>. |
   [Table 3. JWT Provider form]

   {#create-jwtprovdr-salesforce__table_jpx_g4v_g3b}
4. Right-click the form header, and click Save.  
   The Standard Claims and Custom Claims related lists are displayed.
5. In the Standard Claims related list, enter values for iss, sub, and aud.  
   See [OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration](https://help.salesforce.com/articleView?id=remoteaccess_oauth_jwt_flow.htm&type=5) in [Salesforce Trailblazer forum](https://success.salesforce.com/) documentation for instructions.
6. Click Update.

#### Result

The JWT provider is added to your ServiceNow instance.

### Register Salesforce as an OAuth Provider {#ariaid-title9}

Use the information generated during Salesforce connected app configuration to register Salesforce as an OAuth provider and enable
the instance to request OAuth 2.0 tokens.

#### Before you begin

Role required: admin

#### Procedure

1. Navigate to AllSystem OAuthApplication Registry.
2. Click New.  
   The system displays the message What kind of OAuth application?
3. Select Connect to a third party OAuth Provider.  
   The system displays a blank Application Registries form.
4. On the form, fill in the fields.  
   {#reg-salesforce-oauth__table_alw_kq3_gfb__entry__2}

   | Field | Value required |
   |-|-|
   | Name | Name to uniquely identify the record. For example, enter <kbd class="ph userinput">Salesforce OAuth</kbd>. |
   | Client ID | Consumer key that you generated during the Salesforce connected app configuration. |
   | Client Secret | Consumer secret that you generated during the Salesforce connected app configuration. |
   | OAuth API Script | Optional script to customize the request and response. |
   | Default Grant type | Grant type used to establish the token. Select JWT Bearer. |
   | Refresh Token Lifespan | Time, in seconds, that the refresh token is valid. The default time is 8,640,0000 seconds. |
   | PKCE required | Option to enable public clients to require PKCE for an authorization. Note: You can use only Authorization Code as the Default Grant type when PKCE is enabled. |
   | Application | Application scope that contains this record. Select Salesforce. |
   | Accessible from | Application scope that this registry is accessible from. |
   | Active | Option to actively use the application registry. |
   | Authorization URL | This field should be left blank. |
   | Token URL | OAuth server token endpoint. * For production instance, enter <kbd class="ph userinput">https://login.salesforce.com/services/oauth2/token</kbd>. * For sandbox instance, enter <kbd class="ph userinput">https://test.salesforce.com/services/oauth2/token</kbd> {#reg-salesforce-oauth__ul_exw_qr5_fnb} |
   | Token Revocation URL | This field should be left blank. |
   | Redirect URL | This field should be left blank. |
   [ ]

   {#reg-salesforce-oauth__table_alw_kq3_gfb}
5. Right-click the form header, and click Save.  
   * The system validates the OAuth credentials and populates the Redirect URL field.
   * The system populates OAuth Entity Profile with Grant Type as JWT Bearer. For example, OAuth Entity Profile is created with default Name, Salesforce JWT provider default_profile .
   {#reg-salesforce-oauth__ul_gks_4f4_xgb}
6. Copy the value from the Redirect URL field.
7. Click Update.
8. Log in to your Salesforce account to edit the configuration of your connected app.  
   See the [Salesforce Trailblazer forum](https://success.salesforce.com/) documentation for instructions.
9. Paste the Redirect URL value into the Callback URL of your Salesforce connected app.  
   For example, paste <kbd class="ph userinput">https://&lt;instance-name&gt;.service-now.com/oauth_redirect.do</kbd>.

#### Result

The instance can request OAuth 2.0 tokens for the Salesforce spoke.  
Note:  
When an OAuth token expires, the spoke automatically regenerates a new token in most cases. If a token expires and is not regenerated, a user with the admin role can regenerate the spoke OAuth token.

### Create
credential
records for the Salesforce spoke {#ariaid-title10}

Create Credential records
for
the Salesforce connected app
that
you created. The Salesforce spoke connection and credential alias
use these
credentials to authorize actions.

#### Before you begin

Role required: admin

#### Procedure

1. Navigate to AllConnections \& CredentialsCredentials.
2. Click New.  
   The system displays the message What type of Credentials would you like to create? .
3. Select OAuth 2.0 Credentials.  
   The pop-up window displays a blank OAuth 2.0 Credentials form.
4. On the form, fill in the fields.  
   {#create-credrec-salesforce__table_sxv_zgp_gfb__entry__2}

   | Field | Value required |
   |-|-|
   | Name | Name to uniquely identify the record. For example, enter <kbd class="ph userinput">Salesforce Credentials</kbd>. |
   | Active | Option to actively use the credential record. |
   | OAuth Entity Profile | OAuth profile that you created when you registered the Salesforce connected app as an OAuth provider. For example, select Salesforce OAuth default_profile. |
   | Applies to | MID Servers that can use this credential. For example, select All MID Servers. |
   | Order | Order to apply this credential. For example, enter <kbd class="ph userinput">100</kbd>. |
   [ ]

   {#create-credrec-salesforce__table_sxv_zgp_gfb}
5. Save the record.
6. Click the Get OAuth Token related link to generate the OAuth token.

#### Result

The credential record for the Salesforce spoke is created.

### Create connection records for the Salesforce spoke {#ariaid-title11}

Create connection records
for your Salesforce account. The Salesforce spoke connection and credential alias use these connections to perform actions in Salesforce.

#### Before you begin

Role required: admin

#### Procedure

1. Navigate to AllConnections \& CredentialsConnection \& Credential Aliases.
2. Open for the record for Salesforce.
3. On the Connections tab, click New.  
   The system displays a blank HTTP(s) Connection form.
4. Enter these values.  
   {#create-connrec-salesforce__table_any_shp_gfb__entry__2}

   | Field | Value required |
   |-|-|
   | Name | Name to uniquely identify the connection record. For example, enter <kbd class="ph userinput">Salesforce Connection</kbd>. |
   | Credential | Credential record you that created for Salesforce. For example, select Salesforce Credentials. |
   | Connection alias | Alias record associated with this connection. |
   | URL builder | Note: Do not select the check box. |
   | Connection URL | Base URL to connect to your Salesforce instance. For example, <kbd class="ph userinput">https://&lt;instance-name&gt;.salesforce.com</kbd>. |
   | Use MID server | Option to use a MID Server. If you select this check box, define the fields in the Advanced MID Server Configuration related list. |
   | Active | Option to actively use the connection. |
   | Domain | Domain that the action or activity runs in. |
   [ ]

   {#create-connrec-salesforce__table_any_shp_gfb}
5. Right-click the form header and click Save.
6. Ensure that api_version is set <kbd class="ph userinput">v48.0</kbd> in the Attributes related list.

#### Result

The Salesforce spoke is set up and integrated with the ServiceNow instance.

*[\>]: and then