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 a pipeline. 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.

Note: You cannot use jinja expressions in trigger conditions unless explicitly specified as possible.

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:

{'7'.EX.'Ragnar Lodbrok'}AND{9.CT.'Erich'}

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.

Filtering on system user fields

Here's how to filter on the system user fields, such as Record Owner and Last Modified By by email. For example, Record Owner >> Email equals ...

If you are filtering by the email property and your filter is equals, not equals, set, not set, the filter will be applied to the webhook on creation, when you turn on your pipeline. This helps reduce the amount of traffic going to pipelines. If you want to use this new behavior you must recreate your webhooks.

Limits

You cannot use more than 250 fields in a Quickbase step.

Resource details

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

Can you build pipelines between two different realms of Quickbase?

Yes. Add a user token for each realm and you can pick which realm (account) when you add a step.