Design intuitive pages

Why pages shape your workflow 

Pages aren’t a UI feature on the side; they fundamentally change your story’s structure.

Without pages, stories can flow pretty linearly:

Webhook → HTTP Request → Event Transform → Email → Done

With pages, stories become interactive:

Page (input) → Action → Page (options) → Action → Page (results)

Pages introduce three design constraints you must consider:

• Timing: Pages can force your story to wait for user input before continuing.

• State: User choices at each page should be preserved for later steps.

• Clarity: Each page becomes part of a guided experience that users rely on to make decisions.

Common page workflow patterns 

Pattern A: Multi-step pages 

Used when you want to break a large input form into multiple steps to reduce cognitive load.

Where it's used: Access requests, onboarding forms, surveys

Example:

Page 1: Collect user's information
↓
Page 2: Collect request details
↓
Page 3: Review & confirm submission

Pattern B: Search → select → confirm 

Where it's used: Lookup tools, “pick an item” flows, enrichment workflows

Example:

Page 1: Search criteria
↓
HTTP Request action: Fetch results
↓
Page 2: Show list of options; user selects one
↓
HTTP Request action: Fetches details for selection
↓
Page 3: Confirmation screen with results

Pattern C: Review & approval flows 

A human approval step fits perfectly between two automated stages.

Where it's used: Financial approvals, system access, policy exceptions, content reviews

Example:

Prior actions prepare data
↓
Page: Employee reviews & chooses (Approve/Deny)
↓
Story continues

Pattern D: Dashboards 

Pages can present a snapshot of story output, especially when users don’t need to respond.

Where it's used: Enrichment summary, SLA metrics, "View results" after bulk processing

Example:

Prior actions prepare data
↓
Page: Displays final results
↓
Send Email action: Sends an email to users with the Page URL included (via the PAGE key) to access the final results

Page design principles 

Here are the principles used across the best customer page workflows:

• One purpose per page: Don’t mix unrelated elements.

• Keep labels simple: Avoid internal jargon. Use the language your users would use.

• Provide micro-guidance: A short sentence at the top of a field gives context: “Choose the employee you’d like to review.”

• Use conditional visibility: Hide advanced fields until needed.

• Validate early: Set page fields to required that are necessary for downstream actions.