This page provides you with instructions on how to extract data from FormKeep and load it into Redshift. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
What is FormKeep?
FormKeep provides form endpoints that designers and developers can use when they don’t want to build and maintain forms themselves.
Getting data out of FormKeep
FormKeep makes its data available through webhooks, which you can set up on FormKeep's Webhooks tab. You provide a URL to send the data to and write your script to POST data to this URL as it's generated.
Preparing FormKeep data
If you don't already have a data structure in which to store the data you retrieve, you'll have to create a schema for your data tables. Then, for each value in the response, you'll need to identify a predefined datatype (INTEGER, DATETIME, etc.) and build a table that can receive them. FormKeep should provide documentation that tells you what fields are provided by each endpoint, along with their corresponding datatypes.
Complicating things is the fact that the records retrieved from the source may not always be "flat" – some of the objects may actually be lists. This means you'll likely have to create additional tables to capture the unpredictable cardinality in each record.
Loading data into Redshift
Once you've identified the columns you want to insert, you can use Redshift's CREATE TABLE statement to define a table to receive all of the data.
With a table built, you might be tempted to migrate your data (especially if there isn't much of it) by using INSERT statements to add data to your Redshift table row by row. Not so fast! Redshift isn't optimized for inserting data one row at a time. If you have a high volume of data to be inserted, you should load the data into Amazon S3 and use the COPY command to load it into Redshift.
Keeping FormKeep data up to date
Once you've set up the webhooks you want and have begun collecting data, you can relax – as long as everything continues to work correctly. You'll have to keep an eye out for any changes to FormKeep's webhooks implementation.
Other data warehouse options
Redshift is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Google BigQuery, PostgreSQL, Snowflake, or Microsoft Azure SQL Data Warehouse, which are RDBMSes that use similar SQL syntax, or Panoply, which works with Redshift instances. Others choose a data lake, like Amazon S3. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To BigQuery, To Postgres, To Snowflake, To Panoply, To Azure SQL Data Warehouse, and To S3.
Easier and faster alternatives
If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.
Thankfully, products like Stitch were built to move data from FormKeep to Redshift automatically. With just a few clicks, Stitch starts extracting your FormKeep data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Redshift data warehouse.