#SalesforceWinter27 [Tip 37 of 40] (Video 2:37) - Mock Action and Subflow Outputs When Testing Fl...

Winter '27 lets you mock the output of Action and Subflow elements when you test a flow. It's in beta.

In Test Mode, you can tell an Action or Subflow element what to return instead of letting it run. Mock a callout action and the flow skips the real HTTP request and uses the response you defined. Mock a subflow and the flow skips running it and uses your output instead. You can type the mock values in, or copy them from a previous debug run.

It works for autolaunched and record-triggered flows.

Product Area: Flow

It needs Flow Test Mode (Beta) turned on in Process Automation Settings. Then, in Test Mode, select the Action or Subflow element, open Scenario Output, and click Use Mock Output. Here it is in action.

win27-mock-output.mp4

How It is Useful

Testing flows with callouts or subflows used to depend on live external systems and full subflow runs. That made results unpredictable whenever a service was down or returned inconsistent data.

Mock outputs let a test check your flow's logic rather than everything it depends on.

Salesforce highlights four cases:

  1. Callouts to rate-limited or unavailable APIs

  2. Apex actions with complex dependencies

  3. Subflows you don't want to run, and

  4. Fault paths that are hard to trigger with live data.

One thing to remember: a mocked element doesn't run. A passing test proves your flow's logic, not the integration. You still need an end-to-end test against the real system before you go live.

References & Useful URLs

  • For Related Winter '27 Release Note Article – Click Here



Found this useful? Hit like, and drop a comment — I read every one, and your feedback decides which tips make the list.