Collect Google Form responses
This is a 'Workflow' template which means that it is a single standalone workflow.
Some workflow templates can be modified to work with other workflow templates - e.g. to convert a data sync between two services from uni-directional to bi-directional
Google Forms are commonly used to gather information from colleagues, leads, customers, and other groups.
This workflow takes Google Form Submission Data and formats it for use when a form is submitted. The formatted data can be further used in various ways, and thus, builders can configure the workflow to achieve the desired results.
The following connectors are used in this template. This is provided for reference only - there is no need to read through the linked connector pages, as all you need to know for this template is explained here:
We have included a downstream steps example in the Getting Live section below, demonstrating how to store the formatted data in a third-party service. In this case, we are using Google sheets as a generic placeholder for any service or database you may wish to use.
The image below shows a Google sheet populated with formatted form-data:
This workflow assumes the following:
You have access to Google Forms.
The overall logic of the workflow is:
Google Form Submission This is a webhook step that receives information sent from Google Forms.
Format Google Form Data The object helper removes any special characters or spaces in the Google Form Fields so that they can be easily referenced in your workflow down the line using the Connector Snake.
Set up any downstream steps The processed data can then be used in multiple ways like sending data to Salesforce, sending data through an email, or storing data in any third-party service of your choice.
In order to configure this workflow for use, simply:
The key (and only!) thing that this template does is convert Google Form field names into a format that is universally acceptable by third party services and databases.
It does this by pulling in the form data from
$.steps.trigger.body and using the Object Helpers 'Iterative transform (camelCase)' operation:
As you can see from the above screenshot this transforms e.g. "How satisfied were you with the event?" to "howSatisfiedWereYouWithTheEvent".
This format is acceptable as column headers in databases, custom field names etc.
So your workflow will be able to make use of them when adding new form results to e.g. Google Sheets, a CRM, a SQL database etc.