About the Quickbase channel

Quickbase provides a low-code application development platform that helps businesses improve the processes that make them unique, across a variety of industries.

Please note that terms used in the Quickbase channel are Quickbase specific terminology.

Note: If you encounter issues with address fields that contain spaces in the name, please use a jinja expressions using the python key accessor method, for example:{{a.address['Subfield With Spaces']}}

See Pipeline limits for information about system and product limits.

How to connect

  1. On the My pipelines page, click Create pipelines. Enter name, description, and tag fields and click the Create Pipelines button. The pipelines wizard displays:

  2. From the wizard you choose the connections for the first steps of your pipeline. When you choose a type, you'll add the channels and steps for your first steps. You can always add more steps later. A Triggered pipeline is started by a specific event in real-time. A Scheduled pipeline will start according to a schedule. A Manual pipeline only starts manually. Once you've completed the wizard, you'll be prompted for connection detail, if necessary. If you are an experienced builder, click the Start from scratch button and then from the right side of the page, choose the All to list all available channels.
  3. Click Quickbase in the list of channels on the right side of the page and click Connect to Quickbase
  4. Enter your subdomain and user token. When finished, click Connect to Quickbase.

How to reconnect the Quickbase channel

You may need to reconnect your account to a channel. Reasons may be (but not limited to):

  • If you need to connect a different account.

  • Authorization updates, such as a changed password.

  • Editing the access rights that Pipelines has to the channel.

To reconnect:

  1. Select a pipeline that already has Quickbase in it.
  2. Open a step containing Quickbase.
  3. Under account, select Connect (or reconnect) and follow the process above, How to connect.

Create and assign a user token

You can create a user token and assign it to an app at the same time. The token is also available to assign to other apps.

To create a new user token:
  1. On the user drop-down on the global bar, choose My preferences.
  2. Under My User Information, click the link for Manage my user tokens for [subdomain] realm ...
  3. Click the New user token button.
  4. Click OK.
  5. In the Basics section, enter a Name and a Description for your token.
  6. In the Assign token to apps section, click the drop-down arrows to select which apps you want to assign this token to. You can assign a token to as many as 20 apps.
  7. Click Save. The new token appears in the list of user tokens. API calls containing this token can now interact with the application. The new token is also available for assignment to other applications. For more details about managing user tokens, click here.

Steps

The steps you can use with Quickbase fall into a five categories: Records, Quickbase Apis, Attachments, Bulk Record Sets, Automation Admins.

Type Name Description
Records
Trigger Record Created

Triggers when a new record is created in the selected account.

Note: You must have admin rights on the Quickbase app for this trigger to operate.

Trigger Record Updated

Triggers when a record is updated in the selected account. The default is "modify" for "on any event."

You can access a previous record value by dragging-and-dropping the field value you want to access. For example, If you have something like this:{{a.status}} - it will return the new value. When using Jinja, you should add $prev and it will be fetched with the old (changed) data. For example: {{a.$prev.status}}.This is relevant when you have 'on modify', in case of "on add", this will be null. It is advisable to use very specific filters and queries.

Note: You must have admin rights on the Quickbase app for this trigger to operate.

Trigger Record Deleted

Triggers when a record is deleted in the selected account.

Note: You must have admin rights on the Quickbase app for this trigger to operate.

Trigger On New Event

Triggers on any new event on specified table in the selected account. You can select which type of event this step should trigger (on add, update, delete) and you can select one or all of these events. You can access a previous record value by dragging-and-dropping the field value you want to access. For example, If you have something like this:{{a.status}} - it will return the new value. When using Jinja, you should add $prev and it will be fetched with the old (changed) data. For example: {{a.$prev.status}}. This is relevant when you have 'on modify', in case of "on add", this will be null. It is advisable to use very specific filters and queries.

Note: You must have admin rights on the Quickbase app for this trigger to operate.

Action Create Record Creates a new record.
Action Update Record Updates an existing record.
Action Delete Record Deletes a record.
Query Search Records Searches all records in the selected account and returns a list of results.
Action Fetch a Linked Record Fetches a linked record.
Action Look Up Record Searches for a single record by Record ID or by key fields.
Quickbase Apis
Action Make request

Makes an HTTP or REST API request. You can call the Quickbase APIs using your Quickbase authentication (QB-USER-TOKEN) implicitly. An example of usage would be a table-to-table import.

Attachments
Action Upload a File

Uploads a file from a URL to a specific field in a record.

Note: Maximum of 100MB File attachment can be uploaded.

Bulk Record Sets
Action Prepare Bulk Record Upsert Prepares a records for bulk upsert to a specific account and table.
Action Add a Bulk Upsert Row Adds or updates rows in a target bulk record set.
Action Commit Upsert Commits a batched upsert into a Quickbase table.
Action Import with CSV Imports data into the specified table with the given CSV resource.
Action Remove Record(s) Removes records in a Quickbase table based on an advanced query.
Automation Admins
Query Get Automation Information Searches all automations in the selected account and returns a list of results.

Advanced Query

You can filter criteria for your pipeline with query string comparison operators. Query string comparison operators must be in uppercase. You can create queries that find records where the matching value is a certain value that you specify. To create a query that finds a specific matching value, you enter the value in single quotes in the query string, except for placeholder names which use double quotes.

For example:

{'5'.CT.'Ragnar Lodbrok'}AND{'5'.CT.'Acquisitions'}

For more information about operators see Query string comparison operators.

Migration Data

If you are a realm administrator, you can use this resource to get automation migration data to manage the migration statuses of all automations across all apps within the realm.

Resource details

These are the column details returned when pipeline is triggered or run. The trigger_type can be either webhook or schedule.

Type Name Description
Status PENDING Not yet analysed.
  ANALYSING Currently in progress, analysing.
  ANALYSED The automation was analysed.
  ANALYSED_FAILURE Analysed, but with failure.
  MIGRATING Currently in progress, migrating.
  MIGRATED_INACTIVE The automation is migrated, but the pipeline is not yet enabled.
  MIGRATED_ACTIVE The automation is migrated and enabled.
  MIGRATION_FAILURE Migration stopped with errors.
Action Name QB_ADD_RECORD This is the Add a record action step.
  QB_QUERY_AND_EDIT This is the Filter and edit records action step.
  QB_QUERY_AND_DELETE This is the Filter and delete records action step.
  QB_TABLE_IMPORT This is the Table to Table Import action step.
  QB_COPY_RECORDS This is the Copy records from one table to another one action step.