LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • 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
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Templates
  • Choosing a template
  • Starting blank
  • Flow Details
  • Set a Flow name and URL slug

Was this helpful?

  1. Quickstart

Create your first flow

Take a look around your studio and create a new flow.

PreviousKey termsNextAdd content and collect answers

Last updated 9 months ago

Was this helpful?

Click + New Flow to open a dialog box that will give you two options: start from a template or start from blank. The following sections will show you how to navigate either path.

Templates

Choosing a template

Templates allow you to start a flow with added content that serve a specific need, with a default theme to make it look good. There are various templates to choose from - Patient Health Questionnaires, Net Promoter Score surveys, Job Application forms, etc.

If you opt to start with a Template, any flow content included can be modified or deleted down the line.

Starting blank

Once you've selected the theme you want, and you're happy with the flow details, click Create a new flow!


Flow Details

The Flow Details are a set of editable options that can help organize your studio and allow your users to access your form: Flow Name, URL Slug, and Description.

If you've chosen the Pick a Template path (from above), you will also see an embedded example of the template you are going to load into your form. You can test drive this example in the embed before ultimately creating your form with the Use this template button.

Set a Flow name and URL slug

The Flow name is how your flow will be listed in your studio.

Only you and your team will be able to see the flow name, however it will also be used as the default URL slug to navigate to your flow, and is formatted as https://{YOUR-DOMAIN}}/flow/{URL-SLUG}.

If you enable Advanced options you'll see an editable URL Slug field (already be pre-filled with the Flow name) and a Description. Once the flow created the URL slug will be stable and cannot be changed at any time; however you can change the Flow name that is visible in your studio after the flow is created.

Be sure to double check your URL slug before creating your Flow, as you do not want a URL path like the one pictured above to be what you have to send to your users.

Additionally, you can create an optional description for the flow too, for easier differentiation between flows. This, like the flow name, will only be visible to your team in your Studio.

If the Templates have questions that require answers to be calculated, the necessary will be included. For instance, a PHQ-9 template has the required calculated variable to give a score based on responder answers.

Find the template you'd like to start with, and click on it to choose it. Head to for next steps.

If you start blank you'll be taken directly to the Pick a theme step (See below).

Here you'll notice the various themes you can choose from, as well as some editable details for your flow. See below for more information about those details.

If you've already created your flow and forgot to edit the URL slug, see our guide to create a new flow so you can customize the URL slug.

โฉ
๐Ÿž๏ธ
calculated variables
duplicating variants
Flow Details
Themes
Flow Details
You can either pick a template or start from scratch