Environments
Configure integrations.
An environment is a set of integration configurations that govern how a flow interacts with other services, mostly involving sending answers and events.
Environments are defined per flow, and are shared across all variants of that flow, to ensure data integrity between variants.
Clients that are on the Enterprise plan will by default have access to two environments: production and staging, plus the option to create more.
- Production should be used for the "live" version of a flow. Flowstarts are counted when users interact with flows deployed to this environment.
- Staging can be used to integrate with mock or test versions of your integrations, to create a production-like version of a flow that only talks to non-production systems and does not contaminate production data. It is optional to use staging, but for complex forms it is useful to have.
Flowstarts in environments other than production are not counted against your Flowstart monthly limit. Test away!
From the flow index page, the Integrations tab will show the environments editor for each integration.
The integration environment editor
Here it is possible to edit all aspects of integrations, in it's respective environment.
When changes have been made to any of the integrations, you will be prompted to save them.
Updating an environment does not update flows that were deployed to that environment in the past. You must re-deploy flows once the environment is saved.
Accessing the current environment within a flow
It's possible to access the loaded environment (for example,
"production") within a flow using the Formsort environment library answer.Clicking Edit... on the top right of the environment editor shows a list of the current environments and allows the addition of new environments.
Last modified 2mo ago