---
schema_version: "1"
id: c91fc7f8904ffcfd116747438545983fa75f69c54a49188d7edaf7f682ab0c84
title: Invoke a Process from Another Process
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_action_invoke_process.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_action_invoke_process.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0c0d386bd7e75dcc83e9a10ce8197f1546d6400a00e02efe600c661921919e6f
description: Invoke a process from another process. With invocable processes, you have the option of reuse so that you don’t spend your time on repetitive work.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Invoke a Process from Another Process

Invoke a process from another process. With invocable processes, you have the option of reuse so that you don’t spend your time on repetitive work.

### 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_invoke_process__d4787e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_action_invoke_process__d4787e347"><a name="process_action_invoke_process__d4787e347"></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="d233156e84">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="" id="process_action_invoke_process__d4787e977">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d233156e84 ">To create, edit, or view processes:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d233156e84 ">
              <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.").

After you create an action and select “Processes” for the type, fill in the relevant fields to add the action to your process.

You can invoke processes with objects that share at least one unique ID. For example, in the Account and Case objects, the AccountId field is unique to Account and also used by Case. You can create an invocable process that updates a Case record. Then you can invoke it from:

- A process that updates an Account record’s owner
- A process that adds an Account shipping address or updates it

When you create a process that invokes another process, each one counts toward your process and other applicable limits. DML limits in processes that invoke processes count as one transaction.

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

Warning If you create processes to replace any workflow rules, delete those workflow rules when you activate the equivalent processes. Otherwise, both workflow rules and processes fire and cause unexpected results, such as overwritten records or redundant email messages. Do the same if you create processes to replace any Apex triggers.

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. Select an invocable process. You can only select active invocable processes.
3. Select your process variable. Remember that you can only select fields related to the object associated with the process you invoke.