Service Integration

QuickBase Integration – Overview

Already a codeREADr customer? If you also subscribe to QuickBase, you’ll have extensive capabilities for managing all your data in the cloud.

Already a QuickBase customer? If you subscribe to codeREADr, you can quickly & accurately scan barcodes, collect multiple choice & form data, GPS locations, photos, timestamps, etc. Also, you can do that both online and offline, using the native codeREADr iOS and Android apps. Then, insert that data into QuickBase tables.

Not a customer of either service? The integration super-charges QuickBase’s best-in-class cloud service with codeREADr’s native, enterprise-grade app to quickly and accurately scan barcodes and capture, validate and collect associated data into a formal record — anywhere, anytime.

Note: See the SD PRO scan engine add-on here and a blog post here.

Best Practices

There are two ways to use QuickBase with codeREADr.

1.  Direct API Integration

You can use our APIs to automate the process to eliminate manual uploading and downloading files. You create specific tables within QuickBase to automatically insert data captured by your authorized codeREADr app-user(s). Also, the data viewed by the app-user after each scan is current with the data in the associated QuickBase table.

For direct integration, we created a ‘wizard’ for you to simply connect codeREADr to QuickBase. No programming is necessary. Also, you don’t need to learn the codeREADr platform (unless you need special features). All you need to do is associate each QuickBase field to a codeREADr field. From that, we auto-generate the codeREADr ‘Service’ (workflow). Thus,  your authorized app-users can start scanning right away.

What can you do with direct integration? To your QuickBase tables your app-users can:

  1. Add a new record.
  2. Edit an existing record.
  3. Edit existing or add new record IF user inputs at least one value.

<< To launch the wizard click here and for detailed instructions, please read these instructions.

NOTE: You will need to enter your QuickBase Domain (enter just the domain name, not the full URL) and QuickBase App Token to connect to a target table in QuickBase.

Here’s an example of a QuickBase table using the API option. The most important differences include:

  • auto-insertion into key fields (no uploading)
  • scan data from multiple codeREADr Services can be inserted in a single table and optionally in a single row.

In the example below, the Pack, Pick-up, and Delivery tasks were completed by different field workers each scanning the same Tracking ID. The scans records for each are shown in this table in a single row based on the Tracking ID. This enables easier use of formulas for reporting purposes. See the 2-minute video here.

Status Tracking

2. Import/Export CSV

Without using codeREADr or QuickBase APIs. you can create codeREADr Services directly on our web site.

If a record-only type Service (i.e. no database required), simply decide what information you want to collect after each scan. If a validation type Service (i.e. validating against a database of barcode values), determine what information you want to collect after each scan but you need to also import a simple CSV file to codeREADr’s servers. That file includes the barcode values to validate against and any associated content, such as conditions or descriptions for those values.

After scanning, you can filter and export a CSV file of your scan records and import them into QuickBase.

Here’s a CSV export from

Service CSV

And here’s the file after importing to your QuickBase table:

Asset Tracking preview

Once your data is in QuickBase, you can build applications and generate reports.

The CSV option is valuable when the app-user could have slow or unstable Internet connectivity but still needs to quickly both view and validate each scan.

For example, let’s say you need to validate tickets, badges or IDs for an event. If connectivity is slow, lines build up quickly. If you create your Service on codeREADr, the event’s database can be downloaded directly to the app for instant viewing and validation of each ID.

Also, let’s say the app-user needs to know the current condition or status of an asset before updating the record but there’s no Internet connectivity. Likewise, the offline viewing and validation of the asset database is of great value.