Ir para o conteúdo

Salesforce Service Cloud connection

Introduction

A Salesforce Service Cloud connection, created using the Salesforce Service Cloud connector, establishes access to Salesforce Service Cloud. Once a connection is configured, you can create instances of Salesforce activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Note

This connector supports the Enable Re-authentication on Change organization policy. If enabled, a change to the Server Host or Username in this connection requires users to re-enter the Password and Security Token for the connection.

Note

The Salesforce Service Cloud connector is a replica of the Salesforce connector, except for its logo and the name of the connector, connection, and activities. With those cosmetic differences in mind, our documentation on How-tos and Troubleshooting for the Salesforce connector can be applied to the Salesforce Service Cloud connector.

Create or edit a Salesforce Service Cloud connection

A new Salesforce Service Cloud connection is created using the Salesforce Service Cloud connector from one of these locations:

An existing Salesforce Service Cloud connection can be edited from these locations:

Configure a Salesforce Service Cloud connection

Each user interface element of the Service Service Cloud connection configuration screen is described below.

Salesforce Service Cloud connection configuration

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

  • Connection Name: Enter a name to use to identify the Salesforce Service Cloud connection. The name must be unique for each Salesforce Service Cloud connection and must not contain forward slashes (/) or colons (:). This name is also used to identify the Salesforce Service Cloud endpoint, which refers to both a specific connection and its activities.

  • Server Host: Enter the URL of the Salesforce server. If you are using a production instance, leave the default URL as https://login.salesforce.com. If you are using a sandbox instance, select the Sandbox checkbox below.

  • Sandbox: If you are using a Salesforce sandbox instance, select this checkbox to toggle the Server Host field above to https://test.salesforce.com.

  • Username: Enter the username for the Salesforce account. A Salesforce account that does not have multi-factor authentication (MFA) enabled is required.

    To configure a Salesforce account without MFA, make sure that the Permission Set assigned to the Salesforce system integration login does not have the selection Multi-Factor Authentication for API Logins. System integration login types are exempt from Salesforce's MFA requirement, as described by Salesforce in Is MFA required for my integration users? in their documentation Salesforce Multi-Factor Authentication FAQ.

  • Password: Enter the password for the Salesforce account.

    Caution

    A Salesforce password that uses extended ASCII characters, such as £, may cause the following error when fetching data during activity configuration:

    Invalid username, password, security token; or user locked out. [INVALID_LOGIN]
    

    In this case, the connection test may still be successful. If you receive this error during activity configuration and are using special characters in the password, try changing the password.

  • Security Token: If required by the security configuration of the Salesforce instance, enter the security token associated with the Salesforce account. For more information, see the Salesforce documentation for Reset Your Security Token or Unable to see the Reset Security Token option.

  • Test: Click to verify the connection using the provided credentials.

  • Save Changes: Click to save and close the connection configuration.

  • Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

  • Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector basics.

After configuring a Salesforce Service Cloud connection, you can configure one or more Salesforce Service Cloud activities associated with that connection to be used either as a source to provide data to an operation or as a target to consume data in an operation, or you can use the Salesforce Service Cloud connection in a script.

Configure activities

There are eleven activities available, five standard and six bulk activities. Bulk activities should be used only if you do not need to use a transformation to change data prior to reaching the target.

  • Query: Queries data from Salesforce Service Cloud and is intended to be used as a source to provide data in an operation.

  • Insert: Inserts new data into Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Update: Updates existing data in Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Upsert: Both updates existing data and inserts new data into Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Delete: Deletes data from Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Bulk Query: Queries a large number of records from Salesforce Service Cloud and is intended to be used as a source to provide data in an operation.

  • Bulk Insert: Inserts a large number of new records into Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Bulk Update: Updates a large number of existing records in Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Bulk Upsert: Both updates a large number of existing records and inserts a large number of new records into Salesforce Service Cloud and is intended to be used as a target to consume data in an operation.

  • Bulk Delete: Deletes a large number of records from Salesforce Service Cloud and is intended to be used as a target to consume data in an operation. Deleted records are stored in the Salesforce Recycle Bin prior to being permanently deleted.

  • Bulk Hard Delete: Hard deletes a large number of records from Salesforce Service Cloud and is intended to be used as a target to consume data in an operation. Hard deleted records automatically become eligible for deletion.

Use Salesforce Service Cloud connections in scripts

Salesforce Service Cloud connections can be referenced in a script using script functions that use a salesforceOrg as a parameter. For more information, see Use Salesforce functions.