Create custom workflow pages with the Page step

The Page step lets you add a custom participant-facing screen anywhere in an Intellistack Streamline workflow. Use a Page to display instructions, create a pause between steps, provide links to another site, embed third-party content, or replace the generic completion experience with a custom message.

Each Page step displays one screen. From Add item, you can choose Header, Description, Code block, Button, or Next step.

In this article

• Add a Page step
• Header
• Description
• Code block
• Button
• Next step
• Show a loading screen while the workflow processes
• Create a custom completion Page
• Troubleshooting

Add a Page step

1. Open the workflow you want to edit.
2. Select the plus sign on the workflow canvas where you want to add the step.
3. Select Page.

1. Open the Page step to display the Page editor.
2. Select Add item to choose an element.

Note: Each Page step displays one screen. Add another Page step if the workflow needs another custom screen.

Tip: To preview the Page at any point, select Preview in the Build / Preview toggle at the top of the Page editor. Select Build to return to editing.

Header

Use Header for the Page title or another prominent heading.

1. Select Add item.
2. Select Header.
3. Enter the header text.
4. In the toolbar above the header, choose the heading level (H1, H2, or H3) and the alignment (left or center).

Description

Use Description for formatted text, inline images, links, and mapped data from prior workflow steps.

1. Select Add item.
2. Select Description.
3. Enter and format the Page content.
4. Add inline images or links as needed.

Map prior-step data into a Description

1. Open the Description editor.
2. Place the cursor where the mapped value should appear.
3. In the Data panel, locate the field from the prior step.
4. Map the field into the Description at the cursor location.
5. Preview the Page with representative workflow data.

Note: If the mapped field is empty, the Page displays empty space at that location. Header does not support mapped values.

Code block

Use Code block to display vendor-provided content such as a scheduling widget, video, or map inside the workflow session.

1. Obtain the vendor's complete HTML embed snippet.
2. Select Add item.
3. Select Code block.
4. Paste the complete snippet into the code editor.
5. Select Validate and save.
6. Preview the Page.
7. Test the embed in the browsers and session-access modes used by your participants.

Important: A Page does not return embedded-service data directly to the current workflow session. To bring booking details, event data, or other vendor values into Streamline, use an Incoming webhook to start a separate workflow.

Note: Code block is the only Page element that requires a save action. Other Page changes save automatically.

Button

Use Button when participants need a visible, deliberate way to open another site or download a file. A Button has a type, a label, and a destination. The destination is either a URL or a File.

Link to a URL

1. Select Add item.
2. Select Button.
3. Choose the Button type: Primary, Secondary, or Tertiary.
4. Enter the Button label.
5. For Destination, select URL.
6. Enter a complete https:// destination URL.
7. Turn Open in new tab on or off.
8. Add more Buttons if needed. One button group supports up to three buttons.
9. Preview and test every destination before publishing the workflow.

Let participants download a file

Use the File destination to prefill a file into the Page. Participants download the file when they select the Button.

1. Select Add item.
2. Select Button.
3. Choose the Button type and enter the Button label.
4. For Destination, select File.
5. Select the file from the dropdown.
6. Preview the Page and confirm the file downloads when you select the Button.

Note: A Page does not automatically redirect participants or start downloads. Every link and file download requires the participant to select a visible Button.

Note: The Open in new tab option is available for URL destinations only.

Next step

Use Next step when the participant must acknowledge the Page before the workflow advances.

Require participant action

1. Select Add item.
2. Select Next step.
3. Choose the button appearance.
4. Enter the button label.

1. Preview the workflow and confirm that the next step does not begin until the participant selects the button.

Let the workflow advance in the background

Do not add Next step, or remove it from the Page. The workflow advances in the background while the current participant continues to see the Page.

Important: A Page without Next step is non-blocking. Add Next step when the participant must read or acknowledge the content before the workflow advances.

Show a loading screen while the workflow processes

Use a Page as a loading screen when a participant completes a step and the workflow then runs steps that take time before the participant's next task. Common examples are Transform steps that analyze or reformat form data, and steps that generate a document for the participant to sign. Use the Page to show content you configure, such as a status message, instructions, or an image, while these steps run in the background.

This pattern uses a non-blocking Page, so the workflow keeps running in the background while the participant sees the Page.

The following example places a Page before several processing steps:

1. Place the Page immediately after the step the participant just completed, and before the steps that take time.
2. Add a Header that says what is happening, for example "Working on preparing your document."
3. Add a Description that sets expectations, for example "This usually takes a minute or two. Keep this window open." To address the participant by name, map their name from the form into the Description.
4. Optional: add a Code block with a loading animation or other visual, such as a progress bar, an image, or a video. Paste the complete HTML snippet and select Validate and save. See Code block.
5. Optional: add Buttons if you want participants to have somewhere to go while they wait. Set each button to open in a new tab so the participant keeps the workflow window open.
6. Do not add Next step. The workflow continues in the background.

The Page in this example is configured with a Header, a Description containing mapped data, and a Code block containing a loading animation:

What the participant sees

The participant sees the configured message and loading animation while the workflow continues:

The participant stays on the Page while the background steps run. When the participant's next task is ready, such as signing a generated document, they are moved to it automatically. They do not select anything to continue.

The Page stays visible for as long as the background steps take to run. There is no time limit before the participant is moved on.

If the participant's next task is assigned to someone else, the participant stays on the Page and does not see the default handoff screen. The assigned person receives the task through their normal assignment notification.

Create a custom completion Page

A custom completion Page gives participants a clear ending that is specific to your process. Use it when the generic Workflow Completed screen does not provide enough context, or when the participant's work is finished but the workflow still has steps for other people or systems.

A custom completion Page can:

• Confirm that the participant completed their part of the process.
• Display a thank-you message or other process-specific confirmation instead of Workflow Completed.
• Explain what happens next, including whether another person or team must take action.
• Provide Buttons to a support site, scheduling page, payment site, or other destination.

Replace the Workflow Completed screen

Use this pattern when the Page is the final step in the entire workflow.

The following example places a Thank You Page at the end of a webinar registration workflow:

1. Add a Page as the final workflow step.
2. Add a Header and Description that confirm completion and explain what happens next.
3. Add any Buttons the participant may need.
4. Do not add Next step. The workflow completes in the background while the custom Page remains visible to the participant.
5. Preview the complete workflow and confirm that the custom Page appears instead of Workflow Completed.

The Page in this example includes mapped registration details and three Buttons:

The preview shows the completion message and Buttons participants will see:

End the current participant's experience while the workflow continues

Use this pattern when the current participant has finished their work but later workflow steps still need to run or be completed by someone else.

1. Add a Page immediately after the participant's last required step and before the remaining workflow steps.
2. Add a Header and Description that confirm the participant is finished and explain what happens next.
3. Do not add Next step. The workflow advances to the remaining steps in the background while the participant continues to see the custom completion Page.
4. Preview the workflow and confirm that the participant does not need to take another action.

Important: A non-blocking completion Page ends the participant's active experience, but it does not end or cancel the workflow. Remaining steps continue according to the workflow configuration.

Compliance

Vendor HTML runs in a sandboxed, cross-origin frame. It cannot read or change the Streamline application's page, cookies, or browser storage.

Troubleshooting

A Button is rejected

1. Confirm that the destination is a complete, valid https:// URL.
2. Remove malformed redirects or unsupported URL values.

The workflow advances before the participant selects anything

Confirm that the Page contains a Next step button. A Page without Next step advances in the background by design.

A participant stays on a Page and is not moved to the next step

A Page without Next step moves the participant on only when their next task is ready.

1. Confirm that the next step is a task for the same participant, such as a form or a signature. If the next task is assigned to someone else, or no participant task follows, the participant stays on the Page by design.
2. Confirm that the background steps before the next task are completing. The Page remains visible until they finish.