Salesforce Mobile App: Supported and Unsupported Methods for Accessing Flows on Android and iOS

Supported Flow Access Methods in the Salesforce Mobile App

Salesforce for Android and iOS currently supports Flows via the following methods only:

Paused Flow Interviews

The Paused Flow Interviews app is available via: Setup | Mobile Administration | Salesforce Navigation or via Lightning Setup: Apps | Mobile Apps | Salesforce | Salesforce Navigation.

Flow Quick Action

An Object-Specific Quick Action can be created with the type set to "Flow." This is the recommended way to expose Flows to users in the Salesforce Mobile App.
Note: Global Actions and screen-less (auto-launched) Flows are not available via this method at this time.

Flow Interview in a Lightning Component

You can call and work with a Flow from inside a Lightning Web Component (LWC) or Aura Component. This is invoked via the lightning:flow (Aura) component or the lightning-flow (LWC) component and is also available within Lightning Experience.

Methods That May Work (Not Officially Supported)

The following methods may also expose Flows to users in the Salesforce Mobile App, but should be pursued at your own risk as they are not officially supported:

For Visualforce Pages

The Salesforce Mobile App does not support standard components outside the apex namespace (for example, <liveagent:*>, <chatter:*> are not supported). Because Flows utilize <flow:interview> in Visualforce, this approach is not supported and may not render or function as expected.

For Direct URLs

In the Salesforce Mobile App, most Flow direct URLs will display the error: "You can't view this page, either because you don't have permission or because the page isn't supported on mobile devices."

For Hyperlinks in Flow Screens

The Salesforce Mobile App only handles navigation through event-based navigation (e.g., the sforce.one library for Visualforce or lightning:navigation events for Lightning Components). HTML hyperlinks using href attributes in Flow screen output may not work and are not supported. The Flow system also removes any JavaScript embedded in HTML hyperlinks, making event-based navigation impossible from a Flow screen output.