Agentforce, Flow, and MuleSoft can already reach external systems. Orchestrate is complementary when a CRM event should start a long-running process whose durable state, identity chain, approvals, and execution span Salesforce plus ERP, provisioning, billing, ITSM, and custom systems.
Keep the surrounding platform responsible for what it already does well. Use Orchestrate where durable cross-estate execution and one delegation/audit chain become the requirement.
A record transition, event, API call, or upstream process can create the Orchestrate run.
Use Salesforce-supported authentication for CRM calls while binding the larger run to its initiating principal and narrow runtime grants.
Update CRM through supported APIs while the same run executes against ERP, provisioning, billing, support, or custom services.
trigger / delegation / intelligence
durable state · joins · HITL · identity
governed side effect
This sequence illustrates how the integration pattern maps into a durable run. Production topology, permissions, latency, and exact APIs depend on the customer's environment.
A closed-won event creates the durable run with account, product, commercial, and owner context.
Orchestrate invokes ERP customer creation, provisioning, billing, or ITSM tasks as typed tools.
Credit, contract, or provisioning exceptions can route to specialist agents or deterministic rules.
A credit or legal approval can pause the run and resume later from the same checkpoint.
Activation and downstream status are written back to Salesforce with process lineage.
Do not position Salesforce as unable to act outside CRM: MuleSoft for Agentforce explicitly supports third-party systems and cross-enterprise action. Differentiate Orchestrate as a neutral runtime for durable state, identity, and execution across multiple platforms—including Salesforce—rather than as a replacement for MuleSoft, Flow, or Agentforce.
.svg)