This page provides you with instructions on how to extract data from FormKeep and analyze it in Metabase. (If the mechanics of extracting data from FormKeep seem too complex or difficult to maintain, 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.
What is Metabase?
Metabase provides a visual query builder that lets users generate simple charts and dashboards, and supports SQL for gathering data for more complex business intelligence visualizations. It runs as a JAR file, and its developers make it available in a Docker container and on Heroku and AWS. Metabase is free of cost and open source, licensed under the AGPL.
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 Metabase
Metabase works with data in databases; you can't use it as a front end for a SaaS application without replicating the data to a data warehouse first. Out of the box Metabase supports 15 database sources, and you can download 10 additional third-party database drivers, or write your own. Once you specify the source, you must specify a host name and port, database name, and username and password to get access to the data.
Using data in Metabase
Metabase supports three kinds of queries: simple, custom, and SQL. Users create simple queries entirely through a visual drag-and-drop interface. Custom queries use a notebook-style editor that lets users select, filter, summarize, and otherwise customize the presentation of the data. The SQL editor lets users type or paste in SQL queries.
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.
From FormKeep to your data warehouse: An easier solution
As mentioned earlier, the best practice for analyzing FormKeep data in Metabase is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites FormKeep to Redshift, FormKeep to BigQuery, FormKeep to Azure Synapse Analytics, FormKeep to PostgreSQL, FormKeep to Panoply, and FormKeep to Snowflake.
Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data automatically, making it easy to integrate FormKeep with Metabase. With just a few clicks, Stitch starts extracting your FormKeep data, structuring it in a way that's optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Metabase.