Quick Base Reviews

Integration that are natively supported by Quick Base are super easy to set up using their visual builder; no coding or technical know-how required! This library of native integrations is limited but growing steadily, and already has summed it the most used systems such as Office 365 and Google suite.

Additionally, Quick Base also uses web hooks to talk to systems that are not natively supported by their visual builder. This is obviously more complicated and technical in nature, and you’ll need specialised knowledge to use it.

Simple integration utilizing the link (URL) feature in QB to point to SharePoint.

We integrated Quick Base with a MySQL database by working with a Quick Base solutions provider to sync data from Quick Base to MySQL on a nightly and on-demand basis. We are moving many tables and hundreds of fields seamlessly. The integration required defining field mappings because our desired field names in MySQL were different than those in our Quick Base tables, but once each field was defined the project was not difficult.

Our Excel integration involves a button in Quick Base that generates Excel workbooks with data from our MySQL database. The most difficult part of this integration was defining the report format and fields/tables, but once that was established the integration itself was not difficult. Quick Base is very easy to use with other systems, and their engineers and solutions partners are always willing to help make efficiencies and integrations possible.

It wasn't terribly deep. Mostly to link projects to calendars and track progress. It was not difficult at all to achieve and actually integrated quite easily.

With SAP, I tried with middleware based integration using SAP PI and it was a batch processing with the open items from SAP flows to Quick Base in periodic intervals based on mapping done between SAP ERP tables and Quick Base tables.

Also tried integration with in house applications by using SFTP based integration with only the preconfigured data being transferred between 2 systems as feed files.

Some of this integrity is deep, but not too complex. A lot of the information that is passed on is usually an export of a .csv that can be used elsewhere.

Our initial integrations are fairly simple. They are just a few items for each. The process has been easy to use and learn.

We utilized a third party vendor that creates a odbc connection that worked quite well

Sync Tables or as they are also called Connected Tables are extremely easy to setup, a few clicks really and they are done. They update as often as hourly. There are a limited number of Native Connected Tables sources so if what you want is on that list its very easy.

They have just introduced Pipelines, which will have a much broader list of other apps it will connect with. Pipelines are very new and the HELP information is limited, although QuickBase is known to be hard it at to develop the training materials.

Many users have concerns in that the included usage is per "Step Run" - you get some many Step Runs a month and if you run out you need to buy more. So you do need to look at the design to estimate the number of Step Runs to be sure that you don't design a Pipeline which will not be economic. Quick base is somewhat betting the farm on Pipelines so they will work out the issues. But they hold very exciting promise to be able to connect many complex system even like SAP or ODBS data based in a no code method.

QuickBooks Desktop and Online
It was a one-way sync of inventory, invoice, sales order, and purchase order data.

Custom Software
Two-way sync of scheduling modifications

Trello
Updating and moving a card when QuickBase data changed. They were all achieved using the QuickBase API which is easy to understand and use.

Once all platforms are ready to receive connections from the outside, the setup from there on is simple to establish.

A lot of times, you want things to happen in other applications when a record is created in Quickbase and vice versa. For example, we have a Prospects list in our app and when someone unsubscribes from our email list, we wanted it to unsubscribe in both MailChimp and Quickbase. Programming knowledge was an important aspect of integrating the two systems using both APIs and custom scripting.

none

simple file imports

Mainly to push and pull data. Full interactive map with Google Maps.

Fairly straightforward, no major problems encountered. Level of integration was fairly basic, mainly one way import or export.

Somewhat deep - for various use cases, we've looked to identify ways to expanding access to Quickbase from apps already in use within the enterprise for a customer of ours. With many of these integrations already built in, we were able to integrate Zendesk (for customer support tickets) and Dropbox (for customer file tracking) easily. We've also used these as ways to bypass typical integration time and testing (by no longer having to worry about REST API calls or ETLs) making Quickbase a very simple integration point for our other apps.

It was difficult to integrate at first as I did not know where to begin. After looking at tutorials, my team and I were able to figure out and quick base worked well after it was mapped correctly.

Project files. Training modules

It is fairly easy since QB provides good API on operating data layer.

Regular full back end ETL processes that pull data every few minutes. It was not difficult to achieve with a team of professional ETL developers.