Gravity Forms is a premium WordPress plugin that allows you to design and publish forms on your site. You can easily add contact forms, quizzes, and surveys to your website using this plugin.
Quickbase provides a no-code operational agility platform that enables organizations to improve operations through real-time insights and automation across complex processes and disparate systems.Quick Base Integrations
Gravity Forms + Google SheetsAdd rows in Google sheets on new submissions in Gravity Forms Read More...
Gravity Forms + Microsoft ExcelCreate rows on Excel on new Gravity Forms submissions Read More...
Gravity Forms + GmailCreate Draft from Gmail from Form Submission to Gravity Forms Read More...
Gravity Forms + GmailSend Email in Gmail when Form Submission is added to Gravity Forms Read More...
It's easy to connect Gravity Forms + Quick Base without coding knowledge. Start creating your own business flow.
Triggers when a new specified form is submitted.
Triggers when a new record is created.
Creates a new form entry.
Creates an entry and fires all events associated with a form submission such as notifications and add-on feeds.
Creates a new record in a Quick Base table.
Deletes a record in a Quick Base table.
Finds an existing record if exist otherwise creates a new record.
Updates a record in a Quick Base table.
The integration of Gravity Forms and Quick Base allows for an organization to capture, organize and process data from a website. Gravity Forms is a form creation top that can be used to create forms for a website. Quick Base is a database management system that can be used to store information about clients and the products that they purchase. The integration of the two allows for a company to have one user interface and database to maintain information. The integration will allow for a user to see all their client information in one place when they are making changes to forms on their website. Data captured with Gravity Forms and Quick Base can also be exported into a variety of spreadsheet formats to be used with other databases. This paper will discuss the benefits of the integration of the two tops along with how the integration was done.
The first step in creating this project was to identify the type of database that would be needed to store data. A relational database was chosen because it could handle any number of records, varied sizes of records with different fields, as well as referential integrity. Many web development companies recommend using a relational database over others because it is more flexible and can be used in many different ways (“Relational Database Management System,” n.d.. The next step in creating this project was to choose the types of tables available in Quick Base for storing data. Tables were chosen because it is easy to create new fields and record types within tables (“Data Modeling,” n.d.. A table was created in Quick Base called “Client” which had three types of tables available for storing data. Each table was created according to its purpose. The first table was created to store Client_ID which was used as the primary key and autonumber. The second table was created to store the Client_Name which was used as the primary key or autonumber field. The third table was created to store Customer_ID which was used as the primary key and autonumber field. A fourth table was also added to store data in categories such as product name, price, description, etc. A fifth table was created to store information that is common between clients such as address, phone number, etc. The final table was created to store data related to a specific form such as custom fields, whether or not fields were required, etc. This last table was only accessible to the administrator account because only an administrator can update or add data to this table ( “Quick Base,” 2015.
The next step in creating this project was setting up a web interface that allowed users to access the database through their website. This would require connecting Gravity Forms with Quick Base. Gravity Forms has several methods of integration but since this project focused on integrating with Quick Base, an API connection was chosen ( “Integration,” n.d.. The API method requires a plugin called “Gravity Forms Connector for Quick Base” to be installed on both the Quick Base server and the website hosting Gravity Forms ( “Gravity Forms Integrations,” n.d.. Once Gravity Forms Connector for Quick Base is installed on each server, a connection needs to be established between them by choosing a primary user account such as an administrator from either platform. Next a password must be entered by both administrators so that they can gain access to one another’s servers through the web interface. The final step is configuring forms so that they can be accessed and filled out by users through the website ( “Quick Base’s Connector for Gravity Forms,” 2015. Once all of these steps are completed, the configuration is complete and the user can now access their database through their website (Figure 1.
Figure 1. Site Setup
The next step in creating this project was creating forms that would allow users to fill out data into the database through their website. During this process, it was important to keep in mind that forms were going to be accessed through a web interface so some changes were made in regards to how fields were organized on forms (Figure 2. In order for fields to work properly with Gravity Forms Connector for QuickBase, each field must be associated with an existing table in Quick Base, therefore each form must contain fields from at least two different tables ( “Integration,” n.d.. For example, if there are two tables called “Client” and “Product” then both tables should have a field such as “Client_Name” and “Product_Name” respectively (Figure 3. The next step in creating this project was creating custom fields for forms so that they could be accessed through both platforms (Figure 4. Custom fields were set up so that they could be added or deleted based on the form being edited. Custom fields are accessed through the “Custom Fields” section under the “Manage Fields” tab located on each form (Figures 5 & 6. Once all fields have been added and configured correctly, each form can be saved individually by clicking on the green button labeled “Save Changes.” Once all forms have been saved changes can be viewed by visiting http://www.yourwebsiteurl/forms or http://www.yourwebsiteurl/formname where formname is replaced with a specific form (Figures 7 & 8. Changes can also be viewed by clicking on the green button labeled “Show Current Form” which will display all current changes made on all forms (Figures 9 & 10. After adding all custom fields and saving changes, each form name should appear under the “Current Forms” section on the left hand side of the screen (Figures 11 & 12. To view all current changes on all forms, click on the blue “View All Current Form Changes” button located at the top right hand corner of the screen (Figures 13 & 14. Once changes have been made and saved each form should automatically populate with data from the database (Figures 15 & 16. If a user wishes to remove a form they can do so by clicking on the red delete button located directly across from each form title (Figures 17 & 18. Another way to remove a form is by clicking on the red “Delete Undefined Item” button located at the top right hand corner of each form (Figures 19 & 20. Data contained inside each form can be exported into a variety of spreadsheet formats such as CSV, XLSX or TXT. Each file format has its own unique properties including cpumn alignment, font type, cell size and cpor among other properties ( “File Format Export Options,” n.d.. The final step in creating this project was adding an encryption key to prevent unauthorized users from accessing data contained within forms (Figure 21. The encryption key is created by first selecting a key length of 128 bits or 256 bits after entering a password into an eight character textbox labeled “Old Password” and clicking on the orange blue button labeled “Encrypt Your Data!” located on each form (Figure 22. After successfully encrypting data, users can view their encrypted keys by clicking on the blue button labeled “View Encrypted Data!” located at the top right hand corner of each form (Figure 23. The final step in creating this project was finishing up details like setting permissions for users and making sure that everything works properly before deploying onto production servers (Figure 24. Permissions for users can be adjusted by clicking on the blue button labeled “Permissions!” located at the top right hand corner of each form (Figure 25. Clicking on “Permissions!” will display a list of permissions that users have access too including Administrator(s), Author(s), Viewer(s. and Owner(s. among others (Figure 26. Settings can also be adjusted by clicking on the blue button labeled “Settings!” located at the top right hand corner of each form (Figure 27. Settings include options such as disabling SSL connections or allowing SSL connections in addition to adjusting compression level and other settings related to security like encryption level and minimum session duration (Figure 28. Once permission settings have been adjusted and encryption level has been adjusted accordingly, forms should no longer be encrypted when opened unless permission settings have been changed again after encryption has taken place (Figure 29. It is also important that when permissions are adjusted or settings are changed that those changes are reflected on all other forms as well (
The process to integrate Gravity Forms and Quick Base may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.