Pages in Flows

A Flow can show a page and wait for input. This turns automations into guided processes involving people — approvals, follow-up questions, multi-stage data entry.

The three steps involved

Step	Role
Show page (trigger)	Start Flow and load page
Show page (action)	Displays a page for user interaction
Create link to page	Creates a link to a page in the Flow

Two steps share the same name

The trigger starts the Flow with a page. The action interrupts it partway through.

Pay attention to which tab you're in — Trigger or Actions.

A page as the entry point

The Show page trigger starts the Flow as soon as someone submits a page.

The configuration explains:

Use the link below to open the first page of our Flow. As soon as this page is submitted, the Flow will start.

And on distributing it:

You can also pass on this link, for example as a QR code for easy access, or link to it on your website or intranet.

Suited for: incident reports, orders, applications — anything that starts with an input form.

A page in the middle of a process

The Show page action pauses the Flow. It continues once someone submits the page.

Trigger: Entry via form
   ↓
Email                     →  "Please review"
   ↓
Show page                 →  Flow waits for approval
   ↓
Update entry               →  set status

While waiting, the run has the status Waiting in the history.

"Show page" requires someone to be present

The action shows the page to the person currently operating the Flow. For someone who only has time later, you need a link instead.

Asynchronous via a link

Create link to page generates a link to the running instance. You send this by email — the person opens it whenever it suits them.

Trigger: Entry was changed   (Status = "Approval needed")
   ↓
Create link to page           →  link to this run
   ↓
Email                          →  sends the link
   ↓
Show page                      →  Flow waits
   ↓
Update entry

The path to real approval processes

This combination is the difference between an automation that only runs while someone is watching, and a process that works over multiple days.

The approving person gets an email, clicks the link, sees the data, decides — and the Flow continues.

Preparing a page

A page for a Flow differs from a portal:

Show only what matters

• Show context: what needs to be decided? Set the relevant fields to Not editable.
• Capture the decision: the Decision block, with custom labels for Yes and No, is clearer here than a checkmark.
• Show follow-up questions conditionally: a reason field on rejection — via conditional visibility.
• Assign keys: you access the entered values later via the block's key.

→ Input blocks · Data between steps

Editing the page

In the step editor, there's a Edit page tab next to Settings. So you don't need to switch to the Pages area.

Conversely, a page's settings show under Used in Flows which Flows display it.

When no page is assigned

No UI has been set up for this step. If you need a UI, you can add one in the Flow Editor.

Most common cause: the page was deleted

Always check the Used in Flows section before deleting a page. A deleted page breaks every Flow that shows it — and affected users only see This process step could not be loaded.

Testing

For Flow-bound pages, there's a dedicated test path: With data from the Flow form — Open the form and test with submitted data.

The most realistic test

Other test types plug in artificial data. This path goes through the real interface and also surfaces errors in the page itself — missing keys, incorrectly set required fields, visibility conditions that never apply.

→ Testing Flows

Next

• Trigger
• Actions
• What are Pages