LogoLogo
Back to studio
  • 🧠Core Concepts
    • Introduction to Formsort
    • Formsort quickstart guides
      • Add content and collect answers
      • Capture demographic data
      • Add informational content
      • Template your variables
      • Add conditional logic
      • Using conditional logic with Calculated and API variables
      • Add a scheduling option
      • End the flow
      • Review your variable schema
      • Set up integrations
    • How data works in Formsort
      • Responder UUIDs
    • Understanding flows
    • Versioning in Formsort (Deploying)
      • Variant revisions
      • Managing revisions
  • ✨Creating Flows
    • Building a new flow
      • Groups
      • Steps
      • Copy-pasting form content
  • Adding questions and content
    • Questions
      • Select
      • Text
      • Address
      • Comparison
      • Confirmation
      • Date
      • Date & time
      • Email address
      • File upload
      • Grid choice
      • Iframe
      • Image upload
      • Number
      • Payment
      • Phone number
      • Postal code
      • Question group
      • Region
      • Signature
      • SSN
      • Yes/No
    • Content
      • Statement
      • Image
      • Next button
      • Video
      • Divider
      • Map
  • Controlling the flow with conditions and logic
    • Advanced logic
  • Variable templating
  • Redirects and endings
  • Field validation
  • Flow and variant management
  • Content library
  • 🧬JSON Form Definition
  • JSON schemas
  • Validating flow schemas
  • Events subscriptions
  • Flow content data format
  • 🎨Styling
    • Customizing appearance
      • Content area & form layout
      • Buttons
      • Typography
      • UI states
      • Color and dimension variables
      • Question containers
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
      • Animations and transitions
  • CSS & Advanced Styling
    • Custom CSS overrides
    • Step styling
    • CSS reference
  • 🔁Form Behavior Settings
    • Variant settings
      • Form behavior for returning users
      • Group ranking API
    • Navigation sidebar
  • ⚙️Response Data Collection & Management
    • Schema (variables)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
  • Saving & retrieving responses
  • Importing Data
    • URL parameters
    • POST body
    • Embed query parameters
  • 📊Analytics and Attribution
    • Built-in analytics
    • Split testing
  • 🚀Publishing and Deployment
    • Live preview overview
    • Environments
      • Loading different environments
    • Embedding
      • Web-embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Pre-deployment checklist
  • 📁Workspace Management
    • Accounts
      • Roles and permissions
    • Custom domains
    • Workspace domain detection
  • 🛠️Formsort Admin API
    • Admin API
  • 🔌Integrations
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
Powered by GitBook
On this page
  • What do environments do?
  • Editing environments
  • Creating new environments
  • Saving and propagating changes
  • Deploying your variants to different environments

Was this helpful?

  1. Publishing and Deployment

Environments

Configure integrations.

PreviousLive preview overviewNextLoading different environments

Last updated 21 days ago

Was this helpful?

What do environments do?

In Formsort, environments are spaces you can deploy your variants to for different purposes, and the variant environment it is deployed to will correspond to the environment set up in .

For example, you want to test the changes your team is making to a variant in a mocked "live" environment, but also do not want these changes available to your users. In this case you'll want to set up a staging environment to run testing. First, you'd configure the staging environment endpoints (see editing environments below) to make sure you can receive test answers; then, you'll deploy your variant to the staging environment.

Non-production environments are only available to clients that are on the plan. Enerprise clients will by default have access to two environments: production and staging, plus the option to create as many as are necessary.

  • Production should always be used for the "live" version of a flow. are counted when users load and 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. This is ideal for preventing production data contamination. It is optional to use staging, but for complex forms it is useful to have. Flowstarts do not count in this environment.

  • You can if you need them. Flowstarts do not count in any new environments created. Test away!

Editing environments

Environments are defined per flow, and are shared across all of that flow, to ensure data integrity between variants.

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

Since adjustments are made on a per-environment basis, 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.

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.

Deploying your variants to different environments

After saving the changes you've made to your integrations, your live variants need to be 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 any variants you are using to staging.

When you're ready to test, proceed to . Happy testing!

🚀
Loading different environments
integrations
Enterprise
create new environments
Flowstarts
variants
Newly-created dev environment is available.
Save your changes