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
  • Method 1: Add a redirect
  • Method 2: Use a custom question
  • โ€‹Method 3: Return answers via API choices on a select question

Was this helpful?

  1. Quickstart
  2. Common use cases

Add a scheduling option

If your signup flow includes a scheduling element, there are a few different ways you can direct your responders to select a time.

PreviousDisqualify respondersNextAllow responders to read and accept your company policies

Last updated 1 year ago

Was this helpful?

Method 1: Add a redirect

Redirect out of the flow to a calendar app (like Calendly or Acuity) using a.โ€‹

How to do it:

  • When the responder hits a certain step, they can be automatically redirected, or they can click a Next/Submit button to be redirected to a new URL

  • You can have conditional redirects โ€” so some responders can go to different URLs depending on specific criteria

  • You can add to the redirect URL so you can pass data to the scheduling tool

  • Note that a redirect finalizes the flow, so youโ€™ll have to keep that in mind if you are analyzing flow analytics and/or want them to be redirected back into the flow to finish additional steps. In the case where you want to have the responder continue the flow, you will need to create a different second flow to redirect them into.

Some scheduling applications have their own redirects after an appointment or meeting is scheduled!

This makes it possible to redirect the responder back into a new Formsort flow after they've booked something. You can use to bring in any information about the appointment the responder booked.

Formsort does not currently support redirecting users back in to the same flow that the user was redirected out of. This is because redirecting a user out of a flow will finalize the flow at the step the user is redirected, and users cannot return to finalized flows.

For this reason, we suggest using redirects when it makes sense to finalize one flow, and then redirect the user back into a new flow if they need to continue.

Method 2: Use a custom question

You can also choose to embed a scheduling app directly into your flow as a. A custom question is hosted by you in an iFrame.

The benefits to this is that you can keep the responder journey contained to the flow, so it can feel like a more cohesive experience.

How to do it:

  • Add a to render a calendar app in an iFrame

  • You can create multiple conditional custom questions, or every responder can see the same one.

  • Use the editor on the right sidebar to customize the question further.

  • Use the to collect answers

If this doesn't work for your use case, mark the question as optional.

If you have an API of โ€œavailable timesโ€, you can dynamically generate those choices in a select question.

  1. Navigate to Choices > Load choices dynamically

Note that you'll need to use the in order to allow a responder to proceed through the flow and collect their answers. Otherwise, Formsort has no way of knowing that the question has been completed.

Looking to embed Calendly via a custom question? Check out .

โ€‹Method 3: Return answers via on a select question

Add a question

Choose External API that displays the choices (see more about )

โฉ
๐Ÿ’ผ
๐Ÿ—“๏ธ
Redirect
query params
external variables
custom question
custom question
custom question API
custom question API
this example
API choices
Select
providing choices via API