---
schema_version: "1"
id: d716258e879a5459c35a46cb325bf07a2fe3e025230adad7e87253520146fc6a
title: Automate Updates with Workflow Rules in Salesforce to Salesforce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/business_network_workflows.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.business_network_workflows.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 58113bdd5ecb53a7a9d8bb524097e0daef3c44ac5b7512bc757894e186c5c7fe
description: You can use workflow rules to automate updates to records and connections in Salesforce to Salesforce. You can use workflows for many processes, including updating values on picklists when a connection edits the field. If your organization is set up to automatically accept records, workflow rules are triggered by any field you subscribed to.
products:
  - Sales Cloud
  - Cross Cloud
  - Service Cloud Voice
release: "264"
---
# Automate Updates with Workflow Rules in Salesforce to Salesforce

You can use workflow rules to automate updates to records and connections in Salesforce to Salesforce. You can use workflows for many processes, including updating values on picklists when a connection edits the field. If your organization is set up to automatically accept records, workflow rules are triggered by any field you subscribed to.

### Required Editions

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_tip.png)

Tip You can also use Process Builder to automate your processes. If you want your process to perform an action after you create an S2S record, make sure to create a scheduled action rather than an immediate action to allow S2S time to process the created records. Immediate actions fire before shared record connection IDs are updated, resulting in shared records with no connection IDs. Updates to records without connection IDs cannot reach the subscribing system.

<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: Salesforce Classic</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Contact Manager</strong>, <strong>Group</strong>, <strong>Professional</strong>,
              <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong>
              Editions
            </p>
            <p style="margin-bottom:0;">Workflow is available in: <strong>Enterprise</strong>, <strong>Performance</strong>,
              <strong>Unlimited</strong>, and <strong>Developer</strong> Editions
            </p>
          </td>

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

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_important.png)

Important Salesforce to Salesforce is scheduled for retirement as of Spring ’27. See [Salesforce to Salesforce Retirement](https://help.salesforce.com/s/articleView?id=005103355&type=1&language=en_US).

Workflow rules are only triggered for records shared in Salesforce to Salesforce when you accept a parent record, a child record is inserted, or you are subscribed to the fields that are configured to trigger the workflow rules

Some suggestions for criteria for workflow rules for Salesforce to Salesforce include:

- Received Connection Name field on leads, opportunities, and custom objects
- Current User equals pnet
- Last Modified By field equals Connection User

For example, you can create a task for a user every time a connected organization updates a lead. Create a workflow rule with specific criteria, then add a workflow task.

- Evaluation criteria: Evaluate the rule when a record is: created, and every time it’s edited
- Run the rule when criteria are met.
- Rule criteria: “Lead: Last Modified By equals Connection User”.

When you accept a record, only certain fields trigger workflow rules.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d131606e152">Object</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d131606e155">Fields Triggering Workflows</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Account</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Account Name</li>

              <li>City</li>

              <li>Country</li>

              <li>Received Connection Name</li>

              <li>Sent Connection Name</li>

              <li>State</li>

              <li>Type</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Case</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Case Number</li>

              <li>Priority</li>

              <li>Status</li>

              <li>Subject</li>

              <li>Type</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Contact</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Email</li>

              <li>Last Name</li>

              <li>Mailing Address</li>

              <li>Phone</li>

              <li>Title</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Lead</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Company</li>

              <li>Email</li>

              <li>Industry</li>

              <li>Lead</li>

              <li>Lead Source</li>

              <li>Name</li>

              <li>No. of Employees</li>

              <li>Phone</li>

              <li>Received Connection Name</li>

              <li>Sent Connection Name</li>

              <li>State</li>

              <li>Status</li>

              <li>Title</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Opportunity</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Account Name</li>

              <li>Amount</li>

              <li>Close Date</li>

              <li>Name</li>

              <li>Received Connection Name</li>

              <li>Sent Connection Name</li>

              <li>Stage</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Object" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e152 ">Custom Object</td>

          <td data-label="Fields Triggering Workflows" class="slds-cell-wrap" style="vertical-align:top;" headers="d131606e155 ">
            <ul>
              <li>Connection Name</li>

              <li>Name</li>

              <li>Sent Date</li>

            </ul>
          </td>

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

Sometimes it makes sense to use an Apex trigger instead of a workflow. Suppose that you have a workflow rule that updates field B when field A is updated. Even if your Salesforce to Salesforce partner subscribed to fields A and B, updates to field B that are triggered by your workflow rule aren’t sent to your partner’s organization. This prevents a loop of updates.

If you want such secondary field updates to be sent to your Salesforce to Salesforce partners, replace the workflow with an Apex trigger that uses post-commit logic to update the secondary field.

In bi-directional connections, Salesforce to Salesforce updates are triggered back only on “after” triggers (for example, “after insert” or “after update”), not on “before” triggers.