Connect to a source and destination for data pipelines

PRIVATE BETA

This feature is in private beta. Private beta features are available in private preview to selected customers. Customers must opt-in and be accepted into the beta.

During the private beta, Workato may update its functionality or change its availability without prior notice.

Data pipelines require a source to extract data and a destination to store replicated data. Set up both connections before you configure a pipeline.

After you configure connections, proceed to the Configure a data pipeline guide to set up and define sync settings.

Supported sources and destinations

Data pipelines extract data from the following sources:

• Event streams
• File sources
• Jira
• Marketo
• NetSuite
• Salesforce
• ServiceNow

Data pipelines move data to the following destinations:

• Data lakehouses such as Iceberg or Delta Lake
• Databricks
• Google BigQuery
• Snowflake
• SQL Server

LIMITED AVAILABILITY

Some sources and destinations may be unavailable during private preview. During the private beta, you can:

• Connect to Salesforce: As a source connection to extract data.
• Connect to Snowflake: As a destination connection to replicate data.

Contact your Workato representative for information.

Connect to Salesforce

Complete the following steps to connect to Salesforce as a data pipeline source. This connection allows the pipeline to extract data from Salesforce.

Workato supports only OAuth 2.0 connections for data pipelines. JWT-based authentication isn't currently supported.

1

Select Create > Connection.

2

Search for and select Salesforce on the New connection page.

3

Provide a name for your connection in the Connection name field.

Salesforce connection setup

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Use the Sandbox drop-down menu to specify whether the connection is a sandbox account.

6

Select OAuth 2.0 as the Auth type. This is the default and only supported authentication method for data pipelines.

7

Optional. Expand Advanced settings to configure advanced connection options.

8

Optional. Select a Custom OAuth profile to restrict the connection to specific scopes. This ensures the authentication flow uses the client app linked to the custom profile.

9

Select Connect and enter your Salesforce account credentials when prompted.

Log in to your Salesforce account

10

Select Log In to verify the connection.

Connect to a Snowflake destination

Complete the following steps to connect to Snowflake as a data pipeline destination. This connection allows the pipeline to replicate and load data into Snowflake.

1

Select Create > Connection.

2

Search for and select Snowflake on the New connection page.

3

Provide a name for your connection in the Connection name field.

Snowflake connection

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Enter the Account identifier (opens new window) of your Snowflake instance in one of the supported formats:

• Account name: https://{orgname}-{account_name}
• Connection name: https://{orgname}-{connectionname}
• Account locator: https://{accountlocator}.{region}.{cloud}

Refer to the Snowflake Connecting to your accounts guide (opens new window) for more details.

ACCOUNT LOCATOR FORMAT

Certain locations require you to include the {region} and {cloud} in your account locator URL. For example:

• AWS US West (Oregon): your-account-locator
• AWS US East (Ohio): your-account-locator.us-east-2
• Azure West Europe: your-account-locator.west-europe.azure

Refer to the Using an account locator as an identifier (opens new window) guide for more information.

6

Enter the Warehouse name to define the compute resources for this connection. Refer to the Warehouse considerations section for more information.

7

Enter the Database name for the target Snowflake database.

8

Select an Authentication type:

• OAuth 2.0: Requires a Client ID and Client secret.
• Key-pair authentication: Requires a Snowflake User name, a Private key in PKCS#8 format, and a Private key passphrase if the key is encrypted.
• Username/Password: Requires a User name and Password.

SNOWFLAKE USERNAME/PASSWORD DEPRECATION

Snowflake plans to deprecate single-factor password authentication for users by November 2025.

We strongly encourage you to migrate all existing Username/Password connections to OAuth 2.0 or Key-pair authentication before this date. Existing Username/Password connections will remain operational until the deprecation date.

Refer to the Snowflake connector authentication options section for configuration steps.

9

Optional. Specify a Role for authentication. This role must be an existing role assigned to the user. If left blank, Snowflake uses the default role assigned to the user.

10

Optional. Enter the Schema. If left blank, the default schema is public.

11

Optional. Set the Use improved datetime handling (Recommended) to Yes to ensure correct timezone handling for timestamps.

12

Optional. Define the Database timezone to apply to timestamps without an assigned timezone.

13

Click Connect to verify the connection.