Configure integrations.

What do environments do?

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 the production 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.
  • You can create new environments if you need them.
Flowstarts in environments other than production are not counted against your Flowstart monthly limit. Test away!

Editing environments

From the flow index page, the Integrations tab will show the environments editor for your integrations.
Here it is possible to edit all aspects of integrations:
  • create a new integration environment (e.g. create a "dev" environment)
  • configure setup for a new integration target
  • make updates to existing integration targets
These adjustments are made on a per-environment basis, so your production environment will likely have a different integration configuration than your staging environment.

Creating new environments

Clicking Edit... on the top right of the environment editor shows a list of the current environments and allows the addition of new environments. You will see that a production and staging environment are added by default.
Click + Add environment if you'd like to create a new environment. You can also delete environments in this menu.
Once you've added a new environment, you will see it's availability in the dropdown list of environments.
Newly-created dev environment is available.

Saving and propagating changes

When changes have been made to any of the integrations, you will be prompted to save them, regardless of which environment you are in.
After saving the changes you've made to your integrations, your live variants need to redeployed to the matching environment so that the changes can be propagated to your flow.
For instance, if integration changes have been made in your staging environment, make sure to deploy or redeploy the variant you are using to staging.