Skip to main content

Salesforce

The Salesforce connector lets you connect to Salesforce in Designer. Use the connector to read data from Salesforce objects and write data back to Salesforce from a single connector that works the same way across Alteryx Designer (Desktop) and Alteryx One (Cloud).

Salesforce is available as a data source in the Input Data tool and Output Data tool, and as the standalone Salesforce Input and Salesforce Output tool.

New Connector Version in Designer

The Salesforce connector is now part of the Alteryx One connectors experience. Review the information on this page carefully to ensure you're using the appropriate tools correctly.

If you want to update the Salesforce connector in your Designer workflows, you can use the workflow migration utility.

Salesforce Connector Setup

Salesforce is available in Designer 2025.1.2 Patch 7 or later. If you've previously used the Salesforce connector, see Migration to Unified Connector.

Prerequisites

Ensure you have completed the following prerequisites before proceeding:

Requirement

Detail

Designer version

  • 2025.1 Patch 5, 2025.2 Patch 3, or 2026.1 or later (all features except Built-in and Custom OAuth)

  • 2025.1.2 Patch 7, 2025.2.1 Patch 5, or 2026.1 Patch (all auth methods)

Custom app (OAuth 2.0) setup, if used

A Salesforce Connected App with Client ID, Client Secret, Redirect URI (must match the connected app) and scope

Environment URL

Production (default), Sandbox or, Custom domain

DCM

You must enable DCM in Designer. Go to Options > Advanced Settings > DCM to enable it

Install the Connector

You can easily install the latest version of the Salesforce connector from Designer via the Add-Ons. This is the recommended installation method that allows you to browse, install, and update connectors without leaving Designer or visiting the Alteryx Marketplace.

To install the connector…

  1. In Designer, go to Add-Ons > Manage Marketplace Add-Ons. You will see a list of available connectors.

  2. Select Salesforce Connector and select Install. Designer downloads and installs the package. Designer might require a restart to complete the installation.

  3. After installation and setup are complete, the Salesforce connector is available from the Input Data and Output Data tools.

Set Up a Connection

To connect to Salesforce using DCM...DCM - Designer

  1. Drag the Input Data or Output Data tool to the canvas, and select Connect to Data.

  2. In the Connector Setup, select Create or Browse a Data Connection.

    If you've created a Salesforce connection before, you can select the connection from the Recents tab.

  3. Select + New. From the list of technologies, select Salesforce.

  4. Select Quick Connect and then select Setup Connection. The Connections window opens.

  5. Select +New.

  6. Specify the connection name and the data source name. Select the Environment.

  7. In the Credentials section, select your authentication method, and enter the credential name. For more information, see Authentication Methods.

  8. Select Save.

  9. Select Connect. Salesforce may request authentication.

  10. Select the file to read from or write to in the file browser window.

  11. Select the read or write configuration in the Options window.

  12. Select Confirm to create a connection to the file. You can continue building your workflow.

Input and Output Tools

The Salesforce Input and Output tools are used to read from and write to Salesforce.

Salesforce Input

Salesforce Input reads standard and custom objects. You can read in three ways:

  • Query Builder: Pick an object and select the fields you want to read. The field picker offers a multiselect list with Select All, search by string or substring, a live count of selected versus total fields, and a filter to show only what's selected. A record limit can also be set. Four field modes are available: Read all Standard Fields, Read all Custom Fields, Read all Fields, and Choose Manually.

  • Custom Query (SOQL): Write a SOQL query to read standard and custom objects, including __r relationship fields, then validate it before running. A custom query always returns a single table.

  • Read from Report: Browse and search saved reports, select one report, and parse its results.

Salesforce Output

Salesforce Output writes rows to a standard or custom object. Choose an action:

  • Insert: Add new records.

  • Update: Modify existing records. Requires the Salesforce record ID.

  • Delete: Remove records. Requires the Salesforce record ID.

  • Upsert: Insert new records and update existing ones in a single action.

Output processes records in batches and lets you choose the Salesforce API version. When you use Update, Delete, or Upsert, include the record ID as the primary key in your data.

Object Model

Salesforce stores data in objects, which behave like database tables:

  • Standard objects are built in, for example Account, Contact, Lead, Opportunity, Case, Campaign, Task, Event, and User.

  • Custom objects are created in your org and end with __c, for example Invoice__c.

  • Relationship fields between objects use the __r suffix and can be referenced in SOQL.

Authentication Methods

Salesforce supports three authentication methods. Use the table below to choose the right one for your use case.

Method

Required Fields

Desktop (Flagship)

Cloud (Alteryx One)

Built-in app (OAuth 2.0)

None

Yes

Not available (built-in connection creation is not offered on Cloud)

Custom app (OAuth 2.0)

Client ID, Client Secret, Redirect URI (default http://localhost:1717/), Scope (default api offline_access)

Yes

Yes

Salesforce Credentials (username, password, security token)

Username, Password, Security Token (optional), Client ID, Client Secret

Yes

Yes

Custom domain across all methods

NA

Yes

Not available (custom domain is not supported for all methods on Cloud)

 

OAuth supports both the Authorization Code flow (user to app) and the Client Credentials flow (service principal, for headless or scheduled automation).

Migration to Unified Connector

If you already use the Salesforce connector in Alteryx, read the section below. It walks through what has been changed in the unified version.

Parameter

Legacy Connector

Unified Connector (v6.1.0)

Platforms and Tools

Desktop (Input and Output)

Cloud (Input only)

Desktop (Input and Output)

Cloud (Input and Output, in progress)

Framework

Python SDK (Desktop)

CData ODBC driver (Cloud)

EACD framework (Desktop and Cloud)

Communication / API

Salesforce API v52 (Summer '21)

Salesforce API v61+ (Summer '24)

Auth methods

OAuth 2.0

Username + Password + Security Token

Same methods, with expanded configuration

Connection model

Separate Production / Sandbox / Custom URL choices

DCM, with a single Environment URL field

Key Changes

  • Production, Sandbox, and Custom URL dropdown options have been replaced by a single Environment URL field. Reconfigure any workflow that used this dropdown.

  • Environment URL replaces the old dropdown: https://login.salesforce.com (production, default), https://test.salesforce.com (sandbox), or your custom domain.

  • Salesforce Credentials authentication now also requires Client ID and Client Secret.

  • On Desktop, custom domains now work with all authentication methods (previously OAuth only).

Existing workflows can be migrated using the Alteryx Workflow Migration Utility in Designer 2025.2 Patch 3 or later. For more information, see workflow migration utility.

Note

  • The migration utility is available on Desktop only.

  • After installing the unified connector, you may see both the legacy and unified Salesforce technologies listed in Manage Connections. This is expected during the transition. Use the unified connector for any new work.

Limitations

  • The connector does not support a dry run for reads or custom queries. Run the workflow to retrieve data, or use the SOQL validation step to check a custom query before running.

  • For objects with more than 200 fields, the Read all Custom Fields and Read all Fields modes fail. Use Choose Manually to pick the fields you need, or write a SOQL Custom Query that lists specific fields.

  • A SOQL Custom Query always returns one table. To combine data from multiple objects, join them within the SOQL query, or use multiple Input tools and blend the results in the workflow.

  • Read from Report supports selecting a single Report per Input tool. To read multiple reports, use multiple input tools.

  • The connector uses the Salesforce REST API. The Salesforce Bulk API is not yet supported. For very large reads or writes, expect REST API throughput and Salesforce API limits to apply.

  • The object and field data preview is available on Cloud but not on Desktop. On Desktop, configure fields using the Query Builder field list or a SOQL query.

  • On Cloud, custom domain support across all authentication methods is not available. Use a supported method for your Cloud connection, or connect from Desktop where custom domain works with all methods.

  • The workflow migration utility runs on Desktop only.

  • On Cloud, the built-in app connection creation flow is not offered. Use a Custom OAuth app or Salesforce Credentials on Cloud.

  • The datatypes produced from the same object can differ between Cloud and Desktop.

  • On Cloud, loading a dataset can fail for some objects. If a specific object does not load, try a SOQL Custom Query for that object or reduce the selected fields.

  • The connector is generally available on Desktop. Cloud support is in progress and not yet generally available.

Salesforce Version 6.1.0

Connector Release Version 6.1.0

Version

Description

v6.1.0

  • Requires Designer 2025.1.2 Patch 7, 2025.2.1 Patch 5, 2026.1 Patch 2, or 2026.2 GA for all authentication methods.

  • Uses DCM and communicates via Salesforce API v61+ (Summer '24).

  • DCM-based connections with a simplified connection setup (a single Environment URL, and Custom OAuth that exposes Redirect URI and Scope).

  • Input:

    Query Builder: field Select All, search, count, filter, record limit.

    Read from Report with no record cap.

    SOQL Custom Query with validation.

    Choose API version.

  • Output

    Insert, Update, Delete, and new Upsert action.

    Batch processing

    Choose API version.

  • Fixed an issue where reading from a Salesforce report was limited to a fixed number of records (2000). This works only when using the standard REST API.

  • Fixed an issue where DateTime values were returned as 00:00:00, and empty values are now handled correctly.

  • Select All is now available on the column list.

  • Reusing an idle Custom OAuth DCM connection no longer fails with a token error.

  • Built-in app OAuth now authenticates correctly.

  • Dataset loading can fail for certain objects on Cloud.

  • Preview by schema is disabled for a Salesforce Custom Query.

Connection Type

Alteryx Tools. The latest version is available from the Alteryx Marketplace.

Type of Support

Read & Write

Validated On

ODBC Client Version 2.2.20 also available for the Input and Output Data tools.

Version

Description

v5.1.4

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • DCM is required for running this connector in Alteryx Server.

  • The Salesforce connector defaults Time and DateTime precision to milliseconds to avoid extra trailing zeros, while still supporting nanosecond resolution when required by the workflow. (TPM-4753, TPM-4736)

  • Fixed issue where the Salesforce tools ignored the proxy settings on Server. (TPM-4647)

  • Fixed issue where Server couldn’t run workflows with the Salesforce tools because they were dependent on access tokens from Designer. (TPM-4846)

  • Fixed issue where the Designer Developer Tools exposed secret values in the returned JSON files. (TPM-4788)

v5.1.3

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • DCM is required for running this connector in Alteryx Server.

  • Added support for custom Salesforce domains when using DCM.

  • Improved the authentication.

  • Updated the SDK to version 2.4.2.

  • Updated the API to the latest version.

  • Fixed issue where the Salesforce tools ignored the PAC script when using DCM. (TPM-4620)

  • Fixed issue where the Salesforce Input tool failed to read certain date-type columns. (TPM-4604)

  • Fixed issue where the Salesforce Output tool couldn’t display field mapping for the update operation. (TPM-4519)

  • Fixed issue where the Salesforce tools displayed "Access Denied" if the security token wasn’t created in DCM. (TPM-4507)

  • Fixed issue where the Salesforce tools didn’t have the API version aligned according to the front-end tag. (TPM-4493)

  • Fixed issue where the Salesforce tools couldn’t connect using custom domain. (TPM-4488)

  • Fixed issue where the Salesforce tools warned of unexpected truncation of timestamps. (TPM-4368)

  • Fixed issue where the Salesforce Input tool truncated values when using nested relationship objects in a custom SOQL query. (TPM-4367)

  • Fixed issue where the Salesforce Output tools ran indefinitely if the workflows contains multiple Salesforce Output tools. (TPM-4268)

  • Fixed issue where the Salesforce tools displayed multiple API versions as selectable options. (TPM-4264)

  • Fixed issue where the Salesforce Output tool failed to write data with the insert and update operations. (TPM-4248)

  • Fixed issue where the Salesforce tools couldn’t read percentage data type correctly. (TPM-4174)

  • Fixed issue where the Salesforce tools returned an error with custom date fields. (TPM-4051)

  • Fixed issue where the Salesforce tools returned "Error code 400: Bad request syntax or unsupported method". (TPM-3982)

  • Fixed issue where the Salesforce tools displayed slow performance. (TPM-3919)

  • Fixed issue where the Salesforce Input tool returned the versionData field as a URL instead of a document body. (TPM-3662)

Known Issues

  • Certain fields appear as Null after upgrading to the new version of Salesforce tools. (TPM-4805)

  • SDK connectors ignore proxy on Server (Gallery). (TPM-4647)

  • Designer HMTL developer tools expose secret value in the returned JSON. (TPM-4788)

  • Queries return null records in the Salesforce Input tool. (TPM-4641)

v5.1.2

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • DCM is required for running this connector in Alteryx Server.

  • Updated to run on Designer and Server 2024.1.

  • Fixed issue where Salesforce Input failed after running 45 minutes. (TPM-3556)

  • Fixed issue where the source and description metadate were missing. (TPM-3486)

  • Fixed issue where the Salesforce tools ignored proxy settings. (TPM-3358)

  • Fixed issue where Sales Input returned the "Error code 401: No permission -- see authorization schemes" error. (TDCE-449 and TDCE-361)

v5.1.1

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • DCM is required for running this connector in Alteryx Server.

  • Updated to run on Designer and Server 2024.1.

  • Fixed issue where authentication via Custom OAuth application didn’t work. (TFLN-1912)

  • Fixed issue where Salesforce Input ran indefinitely when configured to read an empty dataset. (TPM-2453)

Known Issues

  • Salesforce Tool 5.1.1 isn’t working on Designer FIPS and Server FIPS. As a workaround, please use version 5.1.0. (TFLN-1982)

  • Source and Description metadata are currently missing in workflow results. (TPM-3486)

v5.1.0

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • Added support for DCM to Salesforce Output.

  • DCM is required for running this connector in Alteryx Server.

  • Salesforce Output is now FIPS capable.

  • Improved performance of the auto-configure feature.

  • Added the dry-run option to Salesforce Input.

  • Fixed issue where Salesforce Input 5.0.10 incorrectly parsed data types. (TFLN-1676)

v5.0.10

  • Compatible with Designer 2021.4.2 Patch 6, 2022.1 Patch 4 and later.

  • Compatible with AMP engine only.

  • Added support for DCM.

    • DCM is required for running this connector in Alteryx Server.

  • FIPS capable.

  • Added support for OAuth authentication and custom domains.

  • Fixed issue where Salesforce Input didn’t show all fields and objects. (TPM-1579)

  • Fixed issue where Salesforce Input incorrectly parsed PAC file. (TFLN-1243)

  • Fixed issue where Salesforce Input didn’t display the configuration window when Designer language was set to French. (TDCE-119)

Known Issues

  • Reports lists only Recent reports, not all the Reports available to the user.

  • Reports return only the first 2000 records.

v4.2.4

  • Fixes defect with Custom Queries failing to parse from the Salesforce Input tool.

  • The Salesforce Input jobs will no longer fail when scheduled or run from the command line.

  • Fixes defect with certificate verification in the Salesforce Input tool.

  • Supports uploading the Salesforce Input tool to Gallery without token.

v4.1.0

  • Added support for connecting through a proxy using auto detection and configuration.

  • Compatible with Alteryx version 2019.2 and up.

v4.0.0

  • Added ability to query Salesforce Reports.

  • Query Builder and Custom Query return all records (including deleted) by default.

  • Add 'IsDeleted=False' in WHERE clause to exclude deleted records.

  • Compatible with Alteryx version 2018.3 - 2019.2.

v3.1

  • Fixes defects for Record Limit under Runtime tab of workflow configuration and passwords containing XML special characters.

  • Compatible with Alteryx version 11.0 - 2018.2.

Version

Description

v1.3.1

  • Updated tool metainfo.

v1.3

  • Updated the Salesforce API version in macro engine.

  • Fixed defect to escape characters correctly.

v1.2

  • DateTime fields are converted to YYYY-MM-DDThh:mm:ss.sss automatically.

  • Fixed issue where the "Table name is required" and "Output operation is required" error messages appeared even though the user was not logged in yet.

Note

  • Make sure you have the AMP engine enabled for the workflows which contain the Salesforce Input tool version 2.2.0 and later.

  • To setup a custom API application for this tool, see this guide.

  • If you want to process a PAC file that routes requests through multiple proxy IPs, use security tokens.

Custom Salesforce Domains

The Salesforce tools support custom Salesforce domains.

To connect to a custom domain manually...

  1. In the Salesforce tools configuration window, select Use custom environment url.

  2. Enter your custom domain in Custom Environment.

To connect to a custom domain using DCM...

  1. Select Set Up Connection. DCM opens.

  2. Select +New. The New Data Source windows opens with Salesforce technology pre-selected.

  3. Select Custom in Environment.

  4. Enter your custom domain in Custom Environment and select Save.