How to Use the Open a Page Action in Flow

Key Takeaways

• Open a Page adds native navigation to Screen Flows.
• Supports Salesforce records and external URLs in new tabs or windows.
• Configurable view mode lets users open records in view or edit.
• No same‑tab option; workaround required for in‑place navigation.
• Eliminates custom actions, reducing development time and maintenance.

Pulse Analysis

Screen Flows have become a cornerstone for automating complex business processes, yet navigating users after a flow completes often required custom Apex or third‑party components. Prior to Summer ’26, admins had to build workarounds to redirect users to newly created records or external sites, adding maintenance overhead and potential security gaps. The Open a Page action addresses this pain point by embedding navigation directly into the flow canvas, aligning with Salesforce’s broader push toward low‑code, out‑of‑the‑box functionality.

The action’s configuration panel is straightforward: select Page Type (Salesforce Record or External Web), supply the Record ID and Object Name for internal pages, or provide a full URL for external destinations. View Mode lets the flow open a record in either read‑only or edit state, while the Where to Open the Page setting offers new browser tabs, windows, or Lightning console tabs. This flexibility supports common scenarios such as confirming a case creation, guiding users to a partner portal, or launching a knowledge article. Administrators should note the current limitation—pages cannot open in the same tab—so a separate navigation strategy may be needed for seamless in‑flow experiences.

From an operational perspective, the Open a Page action reduces the time-to‑value for new automations, as developers no longer need to write and test custom navigation logic. It also improves governance, since standard actions inherit Salesforce’s security model and are easier to audit. Looking ahead, the feature sets a precedent for future flow enhancements that prioritize native user experience. Best practices include using view mode judiciously to match user intent, testing across browsers for tab behavior, and documenting any required same‑tab workarounds to maintain consistency across the org.