---
schema_version: "1"
id: 5678fa728d72333c9c8f623a5f236e391239ed0596651ece0bb0ebeb2c58b62c
title: Launch a Flow from a Process
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_action_flow.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_action_flow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4f8e97370ca8a0b16dc918922e1856ccb52093e138da28bc2fccb221e19ba185
description: Start an autolaunched flow from your process to automate complex business processes. Create flows to perform logic and have events trigger the flows via processes without writing code.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Launch a Flow from a Process

Start an autolaunched flow from your process to automate complex business processes. Create flows to perform logic and have events trigger the flows via processes without writing code.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_action_flow__d3004e95"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_action_flow__d3004e99"><a name="process_action_flow__d3004e99"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d76124e84">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="" id="process_action_flow__d3004e977">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d76124e84 ">To create, edit, or view processes:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d76124e84 ">
              <p>Manage Flow</p>
              <p>AND</p>
              <p style="margin-bottom:0;">View All Data</p>
            </td>

          </tr>
        </tbody>
      </table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

To launch a flow from a process, you must create and activate the flow. The flow must be autolaunched.

1. Enter a name for this action.
    
    This text appears on the canvas and helps you differentiate this action from others in your process. The name truncates to fit on the canvas.
2. For Flow, search for and select the flow that you want to launch from this process.
    
    Only active, autolaunched flows are available.
3. Optionally, click **Add Row** to set values for the flow’s variables.
    
    <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:17.88908765652952%">
              <col style="width:82.11091234347049%">
            </colgroup>
            <tbody>
              <tr class="">
                <td class="slds-cell-wrap" style="vertical-align:top;">
                  <samp class="parmname">Flow Variable</samp>
                </td>

                <td class="slds-cell-wrap" style="vertical-align:top;">
                  <p>Start typing the name of the flow variable whose value you want to set, or
                    click <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_dropdown_icon.png" alt="Drop-down icon"></span> to select
                    a flow variable from the dropdown list. </p>
                  <p>You can set values for any variables
                    in the flow that allow input access.</p>
                  <p style="margin-bottom:0;"><span>However, for a text, picklist, or multi-select picklist
                      variable that isn’t a collection, a value of <code>null</code> is converted to an
                      empty string.</span> in the flow.</p>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" style="vertical-align:top;">
                  <samp class="parmname">Type</samp>
                </td>

                <td class="slds-cell-wrap" style="vertical-align:top;">Select the type of value that you want to set. For example, select
                  <strong class="uicontrol">String</strong> to manually enter the values for a Text
                  collection variable, or select <strong class="uicontrol">Reference</strong> to use the value
                  of a record for a record variable.
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" style="vertical-align:top;">
                  <samp class="parmname">Value</samp>
                </td>

                <td class="slds-cell-wrap" style="vertical-align:top;">
                  <p>Set a value for the flow variable. </p>
                  <ul>
                    <li>For collection variables, use the text entry field to specify a value. The
                      value must match the collection variable's data type. </li>
                    <li>For record variables, use the field picker to select an ID field. The ID
                      must correspond to a record whose object type matches the record variable’s
                      object.</li>
                    <li>For record collection variables, use the field picker to select a related
                      list. The selected records’ object type must match the record collection
                      variable’s object. For example, populate a record collection variable with
                      all child contact records associated with the account that started the
                      process.<p>If the related list is empty when the flow tries to populate
                        the record collection variable with field values from those records, the
                        process fails.</p>
                    </li>
                  </ul>
                </td>

              </tr>
            </tbody>
          </table>
4. Save the action.