Start a New Streamline Session After an Existing Session

You can automatically redirect a user into a brand-new Streamline session as soon as they finish or reach a specific point in an existing session.

The new session can restart the same workflow, for repeating a task like entering multiple patient records, or open a different workflow, to move them into the next stage of a process.

Choosing Your Setup

Before building your steps, decide which setup you need.

Option 1: Simple Redirect (No Data Passed)

Use this setup if the user just needs to go to a new session URL and you do not need to pass any information from their current session into the next one.

What you need: One Outgoing Webhook step in your Origin workflow with Redirect users turned on. You do not need an Incoming Webhook.

Option 2: Data Carry-Over (Data Passed to Next Session)

Use this setup if the new session needs details from the current session, such as an email address, record ID, or patient name, so fields can prefill or trigger specific logic.

What you need: Two Outgoing Webhook steps in your Origin workflow, plus one Incoming Webhook step in the Destination workflow, whether that is the same workflow or a different one.

The guide below explains how to configure Option 2: Data Carry-Over.

How the Setup Order Works

Because the workflows need to exchange data, you will set this up in a five-step sequence:

1. Generate the Webhook URL (Destination Workflow): Create the Incoming Webhook in the Destination workflow to generate its URL. Copy the Test URL - you will use it first to configure and test the Outgoing Webhook in the Origin workflow.
2. Send Test Data & Capture Session URL (Origin Workflow): Create the first Outgoing Webhook in your Origin workflow, enter the Incoming Webhook Test URL as the Endpoint URL, send a test payload, and capture the new session URL returned in the response.
3. Switch to the Live URL for Production (Origin Workflow): After you have captured the session URL from the test response, return to the Incoming Webhook step to copy the Live URL, then replace the Test URL in the first Outgoing Webhook's Endpoint URL with the Live URL so production runs create real sessions.
4. Set Up User Redirect (Origin Workflow): Add the second Outgoing Webhook immediately after the first one in your Origin workflow to redirect the user to the newly captured session URL.
5. Map the Incoming Fields (Destination Workflow): Return to the Incoming Webhook in the Destination workflow to map the test payload fields you sent over in Step 2.

Step-by-Step Setup Guide

Step 1: Generate the Webhook URL (Destination Workflow)

Start in the Destination workflow. This is the workflow of the new session. It can be a separate workflow or the same workflow you are currently in.

1. Open the Destination workflow and add an Incoming Webhook step at the very beginning.
2. Copy the Test URL generated by this step. You will use this as the Endpoint URL when setting up the first Outgoing Webhook step in Step 2 so you can send a test request and capture the response.
3. You will also need the Live URL later, in Step 3, to switch the Outgoing Webhook over to the production URL. You do not need to copy it yet.
4. You will complete the field mapping in Step 5 after finishing your Origin workflow.

Step 2: Send Test Data & Capture the Session URL (Origin Workflow)

Switch to your Origin workflow to build the step that creates the new session and sends data over.

1. Open your Origin workflow and add an Outgoing Webhook step where the new session should trigger.
2. In the General tab:

• Set HTTP Method to POST.

• In Endpoint URL, paste the Incoming Webhook Test URL you copied in Step 1. You start with the Test URL so you can fire a test request and capture the response. You will switch this to the Live URL in Step 3 after the response is captured.

1. In the Body tab:

• Choose Raw (JSON).

• Enter the fields you want to pass into the next session.

For example:

{
  "email": "{{Form.Email}}",
  "record_id": "{{Form.RecordID}}"
}

1. In the Response tab:

• Turn on Wait for a response.

• Click Send Test Request. This fires your sample payload to the Test URL.

• Under Extract Fields in the response tab, locate resumeUrl, and label it Session URL.

Step 3: Switch to the Live URL for Production (Origin Workflow)

The Test URL only acknowledges the request and processes field extraction in the background - it does not create a real session. For production runs, the first Outgoing Webhook step must POST to the Incoming Webhook Live URL so a real session is created and a real resumeUrl is returned.

1. Return to the Destination workflow and open the Incoming Webhook step you created in Step 1.
2. Copy the Live URL generated by this step.
3. Switch back to your Origin workflow and open the first Outgoing Webhook step.
4. In the General tab, replace the Endpoint URL (currently the Test URL) with the Live URL you just copied.

Step 4: Set Up User Redirect (Origin Workflow)

Before leaving your Origin workflow, add the step that automatically moves the user's browser into the newly created session.

1. In your Origin workflow, add a second Outgoing Webhook step immediately after the first Outgoing Webhook step.
2. Configure the step settings:

• Set HTTP Method to GET.

• In Endpoint URL, map the Session URL variable you extracted in Step 2.

• Turn on Redirect users.

1. Publish the Origin workflow.

Step 5: Map Incoming Fields (Destination Workflow)

Now that your Origin workflow is fully built, return to the Destination workflow to finish mapping your incoming fields.

1. Return to the Destination workflow and open the Incoming Webhook step you created in Step 1.
2. Go to Extract Fields. You will see the sample data you sent during your test request in Step 2.
3. Select the fields, like email or record ID, so they are available to prefill forms or power logic in this new session.
4. Publish the Destination workflow.

Troubleshooting

User Is Not Redirected

• Check the second Outgoing Webhook step in your Origin workflow and confirm that Redirect users is turned on.

• Confirm that the Endpoint URL in the second step is mapped to the Session URL captured from the first step.

• Confirm that the first Outgoing Webhook step has Wait for a response turned on.

New Session Starts, But Data Is Missing

• Check the JSON body in the first Outgoing Webhook step to ensure the syntax and field names are correct.

• Open the Incoming Webhook step in the Destination workflow and verify that the fields under Extract Fields are mapped properly.

• Send a new test request from Step 2 to verify the payload structure matches.

The First Outgoing Webhook Fails

• Verify that the Endpoint URL matches the Incoming Webhook URL. While testing, this should be the Incoming Webhook Test URL. For production, this should be the Incoming Webhook Live URL (see Step 3).

• Confirm the HTTP Method is set to POST.

• Ensure the Destination workflow is published and active.

The Redirect Goes to a Test Acknowledgment Instead of a Real Session

• This happens when the first Outgoing Webhook step is still pointed at the Incoming Webhook Test URL at production runtime. The Test URL only acknowledges the request and does not create a real session, so the captured resumeUrl is not a usable session URL.

• Complete Step 3: copy the Incoming Webhook Live URL and replace the Test URL in the first Outgoing Webhook's Endpoint URL, then publish the Origin workflow again.

Important Rules to Keep in Mind

• Placement matters: Place the redirect step after all user-facing steps in the Origin workflow. Once the user is redirected, they leave the current session immediately.

• Two steps are required: The first Outgoing Webhook step creates the session and captures the URL. The second Outgoing Webhook step navigates the user's browser to that URL. In the builder, HTTP Method stays set to GET when Redirect users is on.