Run across environments

Point the same Flows at staging or production with Values, recipes, and tags.

Most suites need the same journeys on more than one environment. Keep one Flow, drive URLs and credentials with Values, then change those Values per Run with a Run Recipe. Use tags only when the journey itself differs between environments.

Use the Flow Builder for this walkthrough.

Put environment data in Values

Create Values for anything that changes by environment, such as:

• BASE_URL

• USERNAME and PASSWORD

• Feature flags or region codes your steps read

Keep the Flow free of hard-coded staging or production URLs.

Use those Values in the Flow

1

Open with the environment URL

Start with Open. In the URL field, type $ and pick BASE_URL (or your Value title).

2

Fill credentials from Values

Add Set value for username and password fields. Use $USERNAME and $PASSWORD from the Value Store.

3

Finish the shared journey

Continue with the same steps you would run on every environment.

Example Flow driven by environment Values

Overwrite Values per environment

Go to Settings → Run Recipes. Create one recipe per environment, or one recipe that iterates over several value sets.

In Value Overwrites, replace the defaults for that Run:

{
  "BASE_URL": "https://staging.example.com",
  "USERNAME": "staging_user",
  "PASSWORD": "staging_secret"
}

For several environments in one recipe, use an array of objects. Add primaryValue so results show which set ran:

[
  {
    "primaryValue": "Staging",
    "BASE_URL": "https://staging.example.com",
    "USERNAME": "staging_user"
  },
  {
    "primaryValue": "Production",
    "BASE_URL": "https://www.example.com",
    "USERNAME": "prod_user"
  }
]

Pro tip: Prefer recipe overwrites for environment URLs and accounts. Tags mark which paths run. They do not store credentials or URLs.

When the journey differs by environment

Some steps exist only in one environment, such as a cookie-consent banner on production.

1. After shared setup, add a Flow Branch.

2. On each path, add Tag Test with an environment tag, such as production or nonprod.

3. Put environment-only steps on the matching path.

4. In each recipe, set Test Case Filters → Include Tags to that environment tag, and keep the Value Overwrites for that environment’s URL and credentials.

For packs that share paths but differ only by data, skip the branch and use overwrites alone. See Build smoke and regression coverage for tag and filter detail.

Related

• Share data with Values

• Run Recipes

• Tag Test

• Build smoke and regression coverage

• Reuse a login session