Knowledge Base - Smart Flows
Knowledge Base - Smart Flows
Breadcrumbs

Salesforce Connector

Overview

Experlogix Smart Flows provides a robust, seamless integration with Salesforce. With the introduction of the Second-Generation Salesforce App, administrators can easily configure and maintain their Salesforce connector without the need for Apex code injections or complex metadata manipulation.

This modern, packaged application delivers a clean, supportable, and versioned integration surface while preserving all existing connector behaviors, such as triggering flows directly from Salesforce records and exchanging data securely. In addition, the app ships invocable actions for Salesforce Flow, so that Salesforce administrators can start a Smart Flow and retrieve its execution status from any record-triggered, screen, or scheduled Salesforce Flow. Because Smart Flows also exposes an MCP server, the same flows can be started by AI agents, including Agentforce.

Connector in a nutshell

Parameters

Details

Connector name

Salesforce

License

Requires Plugin for Salesforce

Required version of Smart Flows

4.28+

Max number per project

1

Available for Single Sign-On

Yes

Support for Individual User Authentication

Yes

Supported authentication patterns

OAuth (both the Authorization Code Grant and the Client Credentials Grant types are supported)

Plugin App

Second-Generation Salesforce App

Plugin App Certified

Yes

Plugin App Installation

Via AgentExchange – automated download during connector setup

Scope

Salesforce Organization

Create New Salesforce Connector

All new Smart Flows projects that enable the Salesforce connector automatically use the new Second-Generation App (v2 model).

During the initial connector configuration, Smart Flows guides you through an intuitive visual interface to:

  1. Connect and authorize your Salesforce environment.

  2. Install the Second-Generation App directly into your Salesforce organization.

  3. Automatically validate your Salesforce edition compatibility and confirm the installation success.

Prerequisites

Before you begin, ensure you have:

  • Smart Flows project version 4.28+.

  • Access to the Smart Flows Project Console with administrative privileges.

  • A Salesforce account with System Administrator permissions to authorize the connection and install AgentExchange packages. Please find detailed information about minimal user permission in a dedicated article: Minimal User Permissions in Salesforce

Create New Salesforce Connector

Follow these steps to create a new Salesforce connector and deploy the Second-Generation App:

  1. Log in to the Smart Flows Project Console.

  2. In the navigation menu, select Control Panel and go to Connectors.

  3. Select the Add Connector button.

  4. From the connector type list, choose Salesforce.

  5. Enter a clear Name and optional Description for your connector, then select Next.

  6. Select Authorize to connect Smart Flows to your Salesforce instance. You will be redirected to the Salesforce login page.

  7. Enter the credentials for your designated Salesforce integration user and select Allow to grant Smart Flows the necessary API permissions.

Note: The Salesforce account used here acts as the integration user for all automated background communication between Smart Flows and Salesforce. We highly recommend using a dedicated Salesforce integration user account with appropriate API access rather than a personal administrator account.

  1. Once authorized, the Smart Flows configuration wizard automatically detects that this is a new integration and prompts you to install the necessary components.

  2. Select the provided installation links for the Core App and the Document Automation App.

  3. Follow the standard Salesforce AgentExchange prompts in the newly opened browser tabs to install both packages into your Salesforce organization.

Important: During or after installation, you must assign the provided Smart Flows Permission Sets (e.g., Smart Flows User, Smart Flows Administrator) to the relevant Salesforce users so they can access the integration features.

  1. After successfully installing both apps and assigning permissions in Salesforce, return to the Smart Flows Project Console and select Next.

  2. Follow the remaining wizard prompts to configure the Smart Flows buttons (choosing between manual or automated installation mode).

  3. Select Finish to save your new connector.

Note: Because new deployments use the Second-Generation App natively, Smart Flows entirely skips the legacy steps of extracting, modifying, and republishing Salesforce metadata.

Reconfigure Salesforce Connector

Overview

After your Salesforce connector is successfully deployed using the Second-Generation App, you may occasionally need to reconfigure it. Common reasons for reconfiguring include updating the AgentExchange packages to a newer version, adding or removing Smart Flows buttons on specific Salesforce objects, or refreshing your authentication credentials.

Reconfiguration Steps

Follow these steps to reconfigure an existing Second-Generation Salesforce connector:

  1. Log in to the Smart Flows Project Console.

  2. Go to Control Panel > Connectors.

  3. Select your existing Salesforce and go to Configure tab.

  4. Model Selection: The wizard asks you to select the connector model version. Ensure v2 (recommended) is selected. (The legacy v1 model is deprecated and should only be selected if explicitly enabled via settings as a temporary escape route).

  5. Authorization: If your OAuth token has expired or you need to switch the integration user, select Authorize and grant access using the appropriate Salesforce integration credentials. If authorization is still valid, you can simply proceed to the next step.

  6. App Management: The wizard will detect that the Second-Generation App is already installed in your Salesforce environment. You will be presented with action choices for the AgentExchange packages:

    • Keep: Leaves the current installed apps exactly as they are. Select this if you only want to update button configurations.

    • Modify / Update: Allows you to install a newer version of the applications from the AgentExchange.

    • Uninstall: Completely removes the apps and customizations from your Salesforce environment.

  1. Choose your desired action (e.g., Keep) and select Next.

  2. Button Configuration: If you chose to keep or update the apps, the wizard will take you to the objects selection stage. Here, you can select new Salesforce objects to receive an Experlogix Documents button, or deselect objects to remove existing buttons.

  3. Choose your preferred Installation Mode (Manual or Automated) to apply these button changes to your Salesforce page layouts.

  4. Select Finish to save and apply the updated connector configuration.

Migrate V1 to V2 Salesforce Connector

If you are an existing customer using the legacy Apex-based connector (v1 model), your current integration continues to function without interruption. However, the v1 model is now deprecated, and we strongly recommend migrating to the Second-Generation App to unlock future updates and ensure long-term compatibility.

While a v1 connector is still configured, Smart Flows displays a deprecation warning in your project.

What Changes During Migration

Migrating does not replace your flows, templates, or data sets. It replaces the way Smart Flows is embedded in Salesforce:

Area

v1 model (legacy)

v2 model (Second-Generation App)

Salesforce components

Buttons, list view pages, and a controller class deployed into your organization as metadata

Delivered by two certified managed packages installed from the AgentExchange

Deployment method

SOAP-based metadata deployment

Managed package installation with version tracking, plus automated button deployment

Object coverage

Determined by the deployed metadata

Explicit object selection in the setup wizard

Permission sets

XpertdocSmartFlowsAdministrator, XpertdocSmartFlowsDesigner, XpertdocSmartFlowsUser

Experlogix Documents Admin, Experlogix Documents Designer, Experlogix Documents User

Important: The v1 and v2 permission sets are independent of each other. A user who holds a v1 permission set does not automatically receive the equivalent v2 permission set. Plan to assign the new Experlogix Documents permission sets as part of the migration.

Prerequisites

Before starting the migration, ensure you have:

  • Smart Flows project version 4.28+.

  • Access to the Smart Flows Project Console with administrative privileges.

  • A Salesforce account with System Administrator permissions, able to install AgentExchange packages.

  • A planned maintenance window, because users temporarily lose access to the Smart Flows buttons while the migration is in progress.

Phase 1: Remove the Legacy Smart Flows Components First

The v1 and v2 models use different Salesforce components. The v2 setup installs its own buttons and pages. To avoid leaving obsolete buttons and pages behind in your Salesforce organization, we recommend removing the legacy Smart Flows components before you switch the connector to the v2 model.

  1. Log in to the Smart Flows Project Console.

  2. In the navigation menu, select Control Panel > Connectors.

  3. Select your existing Salesforce connector > Configure to launch the setup wizard.

  4. On the Select connector model stage, leave v1 (deprecated) and select Next.

  5. On the Environment stage, set Smart Flows buttons in Salesforce to Uninstall and select Next.

  6. Complete the authorization step if you are prompted for it.

  7. On the Uninstall from Salesforce stage, select Remove all Smart Flows objects from Salesforce and select Next.

Important: Make sure that all Smart Flows permission set assignments are removed beforehand. Salesforce blocks the removal of components that are still referenced by assigned permission sets.

  1. The removal can take several minutes. Select Next to check whether the process has completed.

You can then continue with the migration steps below.

Phase 2: Migration Steps

Migrating is not a separate procedure. You reopen the setup of your existing connector, switch the model version to v2, and then complete the regular v2 configuration.

  1. Log in to the Smart Flows Project Console.

  2. In the navigation menu, select Control Panel > Connectors.

  3. Select your existing Salesforce connector > Configure to launch the setup wizard.

  4. On the Select connector model stage, select v2 and select Next.

  5. On the Environment stage, select Production or Sandbox or Custom Domain (If your organization uses a custom login URL, enter it here).

  6. On the Authorization stage, select Authorize and sign in with your Salesforce integration user, then select Allow.
    If your existing authorization is still valid, you can proceed without signing in again.

Note: Smart Flows re-evaluates the Salesforce objects and permission sets in your organization during this step.

  1. Smart Flows detects that the managed packages are not yet installed and offers to install them. Select Install and open the two provided AgentExchange links:

    • Experlogix Cloud Connect for Salesforce (the Core App), which delivers the components shared by all Experlogix Cloud Connect products, such as permission sets and logging.

    • Experlogix Cloud Connect - Document Automation Extension (the Document Automation App), which delivers the Smart Flows integration itself.

  1. In the AgentExchange installation screen, choose an installation security option:

    • Install for Admins Only - recommended. Access is then granted deliberately through the Experlogix Documents permission sets.

    • Install for All Users - every internal profile receives access.

    • Install for Specific Profiles - lets you map access profile by profile.

  1. Complete the installation of both packages, then return to the Smart Flows Project Console and select Next.

Note: If you select Skip instead of Install, the connector is still saved and can read Salesforce data, but Salesforce cannot call Smart Flows. The Smart Flows buttons and the Salesforce automation actions are unavailable until the packages are installed.

  1. On the Button installation stage, choose an installation mode:

    • Automated - Smart Flows retrieves your Salesforce metadata, lets you select the objects, and deploys the buttons for you.
      In Automated mode, wait for the metadata retrieval to finish, then select the Salesforce objects that should receive a Smart Flows button. The most commonly used objects are pre-selected. Select Next and wait for the deployment to complete.

    • Manual - Smart Flows makes no layout changes; you add the button to your page layouts yourself.

  1. On the Configuration stage, review the two options:

    • Update the configuration record in Salesforce (selected by default) - writes your Smart Flows project URL and a freshly generated service account API key into the Connection Settings record in Salesforce. Keep this selected, because Salesforce cannot call Smart Flows without it.

    • Assign the Smart Flows administrator permission set - assigns Experlogix Documents Admin to the Salesforce user you authorized with. This option is shown only when that user does not already hold the permission set.

  1. Review the Summary stage and select Finish to save the migrated connector.

Phase 3: After the Migration

Complete the migration in Salesforce:

  1. Go to Setup > Installed Packages and confirm that both packages are listed with the expected version.

  2. Open the App Launcher, go to Experlogix > Connection Settings, and confirm that the record contains your Smart Flows project URL and an API key.

  3. Go to Setup > Users, open the connector user, and confirm that Experlogix Documents Admin appears under Permission Set Assignments.

  4. Assign the appropriate Experlogix Documents permission set to your end users. Users who previously held a v1 permission set do not receive a v2 permission set automatically.

  5. Open a record of one of the selected objects and confirm that the Smart Flows button is present and opens the execution panel.

Note: After completing these steps, the connector functions identically from the end-user perspective. All existing flows and templates will continue to work seamlessly with the newly installed Second-Generation App.

Troubleshooting Installation Errors

If the Second-Generation App cannot be installed, the connector setup fails gracefully and provides clear messaging in the Project Console to help you resolve the issue. Common installation errors include:

  • Missing permissions: The Salesforce user authorizing the connection lacks the necessary administrative rights to install packaged apps.

  • Blocked managed package installation: Your Salesforce organization policies currently restrict or block the installation of third-party managed packages.

  • Version conflicts: An incompatible version of the application or its components already exists in your Salesforce environment.