Need to get FormKeep data to your warehouse? You’ve come to the right place! This page will give you the tools you need to do just that. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
Collecting FormKeep Data
The first step for getting your FormKeep data into Redshift is collecting that data from FormKeep’s servers. You can do this using Webhooks. You can set up a webhook by logging into your FormKeep account and clicking the “webhooks” tab. Data from FormKeep is retrieved via user-defined HTTP callbacks. You will provide a url to send the data to and design your script to listen on this URL.
Sample FormKeep Data
Once you’ve set up HTTP endpoint, FormKeep will begin sending data via the POST request method. Data will be enclosed in the body of the request in JSON format. The fields and endpoints will match the data collected by your form.
Preparing FormKeep Data for Redshift
With the JSON in hand, you now need to map all those data fields into a schema that can be inserted into your Redshift database. This means that, for each value in the response, you need to identify a predefined data type (i.e. INTEGER, DATETIME, etc.) and build a table that can receive them.
Next, use the CREATE TABLE statement in Redshift to define a table that can receive all of this data.
Inserting FormKeep Data into Redshift
It may seem like the easiest way to add your data is to build tried-and-true INSERT statements that add data to your Redshift table row-by-row. If you have any experience with SQL, this will be your gut reaction and it will work but isn’t the most efficient way to get the job done.
Redshift actually offers some good documentation for how to best bulk insert data into new tables. The COPY command is particularly useful for this task, as it allows you to insert multiple rows without needing to build individual INSERT statements for each row.
If you cannot use COPY, it might help to use PREPARE to create a prepared INSERT statement, and then use EXECUTE as many times as required. This avoids some of the overhead of repeatedly parsing and planning INSERT.
Keeping Data Up-To-Date
So what’s next? You’ve built a script that collects data from FormKeep and moves it into Redshift. What happens when FormKeep sends a data type that your script doesn’t recognize? It’s also important to consider the situation where an entry in Redshift needs to be updated to a new value. Once you’ve build in that functionality, you can set your script up as a cron job or continuous loop to keep pulling new data as it appears.
Other Data Warehouse Options
Redshift is totally awesome, but sometimes you need to start smaller or optimize for different things. In this case, many people choose to get started with Postgres, which is an open source RDBMS that uses nearly identical SQL syntax to Redshift. If you’re interested in seeing the relevant steps for loading this data into Postgres, check out FormKeep to Postgres
Easier and Faster Alternatives
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 solve this problem automatically. With just a few clicks, Stitch starts extracting your FormKeep data via the webhook API, structuring it in a way that is optimized for analysis, and inserting that data into your Redshift data warehouse.