Docs
Environments
Reuse the same flow with different variables. Switch the environment at play time — payment × staging vs prod, or two configs of the same journey.
Same flow, different values
An environment is a named set of variable values. The steps stay the same. The data changes when you hit Play.
Typical split:
- Staging —
{BASE_URL}points at staging, a QA user, test payment details - Prod smoke — production host, a dedicated smoke user, no real charges
When to use one
- The same journey against more than one host
- Alternate users, locales, or feature flags
- Payment × currency, plan, or other config matrix
If only one value ever exists, a single variable is enough. Add an environment when you would otherwise duplicate the whole flow.
Play time
Choose the environment when you play a flow or a folder. Do not bake a host name into a recorded navigation if you already know you will switch.
Local only
Environment names and values sit in IndexedDB with everything else. Switching environment does not talk to our servers — there are none. A prod environment in the extension is still you, in Chrome, hitting the URL you configured.