Cloudastick Systems

Cloudastick Blog

Insights & Updates from the Cloudastick Team

March 24, 2026

Auto-Refresh Lightning Pages with Salesforce Flow

Introduction

When working with Screen Flows in Salesforce, keeping the page fully up to date can be a challenge—especially when multiple components depend on the same data.

You might update a record using one flow, only to find that another component on the same page still displays outdated information. This creates confusion and breaks the user experience.

This guide walks through a simple and effective solution: triggering a page refresh directly from your flow.


The Problem

In many real-world scenarios:

  • Screen Flows are placed on Lightning record pages
  • Multiple components (flows, related lists, widgets) exist on the same page
  • A flow updates a record successfully

However:

  • The updated field reflects immediately
  • Other components do not refresh automatically
  • Users see inconsistent or outdated data

Example Scenario

Consider a Case record page with two flows:

  1. Flow A
    • Displays a table of open cases related to a contact
  1. Flow B
    • Allows the user to update the contact on the case

What happens without a refresh:

  • The contact is updated using Flow B
  • The record page shows the new contact
  • Flow A still displays the previous contact’s cases

Result:

  • Data mismatch
  • Confusing user experience

The Solution: Page Refresh Flow Action

A custom Flow Action (Lightning component) can be used to:

  • Refresh the entire Lightning page
  • Reload all components
  • Ensure all data is consistent

This works exactly like a manual browser refresh (F5), but is triggered automatically within the flow.


How to Implement

1. Install the Component

Use the appropriate link for your environment:

  • Production / Developer Edition
  • https://login.salesforce.com/packaging/installPackage.apexp?p0=YOUR_PROD_LINK
  • Sandbox
  • https://test.salesforce.com/packaging/installPackage.apexp?p0=YOUR_SANDBOX_LINK

2. Add the Action to Your Flow

  • Open your Screen Flow
  • Add a new Action element
  • Search for: ReloadPage
  • Select the action

3. Place It in the Flow

  • Add the action at the end of your flow

or

  • Place it right after a key update step

Key Characteristics

  • No configuration required
  • No input parameters
  • Instantly refreshes the current page
  • Re-runs all components and flows on the page

When to Use This

This approach is especially useful when:

  • Multiple flows exist on the same page
  • One flow updates data used by another
  • You rely on dynamic components or data tables
  • You want to avoid manual user refresh

Benefits

  • Eliminates stale or inconsistent data
  • Improves user experience
  • Keeps all components aligned
  • Reduces confusion and support issues

Conclusion

When building Screen Flows, it is important to think beyond just updating records. Ensuring that the entire page reflects those updates is equally critical.

By adding a simple page refresh action, you can create a smoother, more reliable experience where users always see accurate and up-to-date information—without needing to refresh manually.

March 24, 2026

Bring External Content into Salesforce Flows

Introduction

Keeping users inside Salesforce while still giving them access to external tools or content can be challenging.

In many business processes, users need to interact with external systems such as forms, dashboards, or third-party tools. Redirecting them outside Salesforce disrupts the experience and breaks the flow.

This guide introduces a simple solution: embedding external content directly inside a Screen Flow using an iFrame component.


What is an iFrame

An iFrame (inline frame) is an HTML element that allows you to display one web page inside another.

In Salesforce, this means you can:

  • Show external websites inside a Screen Flow
  • Integrate third-party tools without leaving the platform
  • Keep users within a guided process

The Limitation in Salesforce

Salesforce does not provide a standard iFrame component for Screen Flows.

Common workarounds:

  • Lack flexibility
  • Do not support dynamic URLs
  • Make it difficult to pass record-based parameters

This makes it harder to build seamless, integrated user experiences.

The Solution: iFrame Screen Flow Component

A custom Screen Flow component enables you to:

  • Embed external content directly into a flow screen
  • Configure size and layout easily
  • Use dynamic URLs based on records or user input

How to Implement

1. Install the Component

Use the appropriate link for your environment:

  • Production / Developer Edition
  • https://login.salesforce.com/packaging/installPackage.apexp?p0=YOUR_PROD_LINK
  • Sandbox
  • https://test.salesforce.com/packaging/installPackage.apexp?p0=YOUR_SANDBOX_LINK

2. Add the Component to a Screen Flow

  • Create or open a Screen Flow
  • Add a Screen element
  • Drag and drop the iFrame Component

3. Configure the Component

Set the properties based on your needs:

  • iFrame URL
    • The external page to display
  • Height
    • Default: 600px
  • Width
    • Default: 100%
    • Supports pixels or percentage
  • Show Border
    • Enable or disable the frame border

Important Configuration: Trusted URLs

Before using the component, you must allow the external domain in Salesforce.

Steps:

  • Go to Trusted URLs (CSP Trusted Sites)
  • Add the domain of your iFrame URL
  • Ensure the URL uses HTTPS

Notes:

  • Some websites block iframe embedding using security headers
  • Even if the domain is trusted, these sites may not display inside Salesforce

Example Use Cases

1. Display External Content

  • Show external pages or profiles directly on a record page
  • Useful for quick access without navigation

2. Embed Forms in a Business Process

Example flow:

  1. Create a new Account
  2. Display an external form inside the flow
  3. Collect user input (such as a signature)
  4. Continue the process within Salesforce

When to Use This

This component is ideal when:

  • You want to integrate external tools into Salesforce
  • You need a seamless, guided user experience
  • You want to avoid redirecting users outside the platform
  • You need to pass dynamic data into external pages

Benefits

  • Keeps users inside Salesforce
  • Improves process continuity
  • Enables external integrations within flows
  • Creates more interactive user experiences

Conclusion

Embedding external content inside Screen Flows allows you to extend Salesforce beyond its native capabilities.

With an iFrame component, you can build more connected, efficient, and user-friendly processes—without disrupting the user journey.