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
  • When to use Google Sheets
  • Authentication
  • Frequency
  • Schema and Insertion Rules
  • Setting up Google Sheets

Was this helpful?

  1. Handling data
  2. Integration reference

Google Sheets

This integration allows you to quickly setup and send responder answers to a Google sheet.

PreviousGoogle Cloud StorageNextGoogle Tag Manager (GTM)

Last updated 2 years ago

Was this helpful?

When to use Google Sheets

You should consider Google sheets if:

  • You or your business uses the Google suite of products

  • The traffic to your form is low (<20 responders a day). Using Google sheets will count towards your . Formsort cannot guarantee delivery of responses if this limit is reached.

  • You have a one-off form for a small use case

  • You need to quickly get your form up and running, and you have no engineering resources

  • Youโ€™re a healthcare business that needs HIPAA compliance and have signed a Business Associate Agreement (BAA) with Google Workspace products. Google Sheets uses high-level encryption to safeguard protected health information (PHI), but you still need to sign a BAA as this data will be stored on Googleโ€™s servers.

You should consider a database () if:

  • You have high traffic volume to your form

  • You have concerns that data in the Google sheet will be edited or deleted. Remember that whoever has access to the sheet can modify data.

  • You want the durability, consistency, and query capabilities of a traditional database

  • Youโ€™re a healthcare business that needs HIPAA compliance but havenโ€™t signed a BAA with Google Workspace products.

If any of the above statements are true, you should store responder data in a traditional database. For these needs Formsort offers integrations for BigQuery, PostgreSQL, and Redshift. For anything else, you can use our webhook integration.

Authentication

  • A Google account is required to authenticate the integration and to insert answers.

  • Edit permissions are required for the sheet, and losing permissions or access to the sheet will cause answers to not be recorded.

Frequency

The frequency of inserting a row to Google Sheet can be configured as:

  • On Finalize: only at the end of the flow.

  • Debounced: when the responder abandons the flow after a period of inactivity, and at the end of the flow. Formsort recommends using this setting to reduce the load.

Schema and Insertion Rules

When creating your flow, the questions and corresponding variables will automatically create the response schema that will be transposed into the sheet. Each variable in a flow will be mapped to a single column in the sheet.

When inserting to an empty sheet, the first row is written as a header row following the defined flow schema. Following responses will appear beneath in the corresponding columns.

If the schema is updated, following insertions will write in the order of their appearance within the flow. If a column is deleted or edited within the sheet, and the flow contains the variable, a new column will be created in the first empty column that is found.

If a flow variable is edited or deleted, Formsort will not update the google sheet. The existing corresponding column for a deleted variable will be skipped on future insertions.

All insertions will use the default formatting options for the sheet.

All variables will be sent to the sheet. Future improvements will allow a user to select which response variables to send.

Setting up Google Sheets

Note: To use the Google Sheet integration you must have an existing flow.

  1. Turn on the Google Sheets integration

2. Connect your Google account and accept all access options. This is required for the integration to work. Formsort will never access information that has not been explicitly set in the integration.

4. Test and save

You can test the connection on demand by sending an example payload to your selected Google sheet.

When you are ready to deploy, be sure to Save your work with the button in the top right corner.

Note: The Google Sheets integration will use your, and Formsort cannot guarantee response delivery if this quota is reached.

3. Select which sheet to send the responses to and .

If you have deployed flows previous to integrating with or updating your Google Sheets integration, it is advisable to re- those flows.

๐Ÿ’พ
Google API limits
full list of supported options
Google API quota
deploy
how often