Resources · Make integration

Quickbase Make integrationAutomate Quickbase with Make.

Tired of building the same Quickbase apps and tables by hand? The Quickbase Make integration gives you 15 modules, 13 actions and 2 searches, all about structure. This guide is for ops teams who run Quickbase and walks you from the connection to a first working scenario.

Try the Quickbase integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Quickbase Make integration do for you?

The Quickbase Make integration links your Quickbase account to Make, a visual tool where you chain apps into a scenario (the automation you build). Its modules, the bricks of a scenario, work on the structure of Quickbase: they create, read, update and delete apps, tables and fields. You pick a module, fill a few boxes and test, with no code.

A ready workspace for each new project. When a deal closes in your CRM, Create an App opens a Quickbase app for that client, Create a Table adds the tables your team expects, and Create a Field sets up the columns. The project manager opens a finished structure instead of a blank one.

A map of what already exists. List Tables and List Fields return everything inside an app, one bundle (one item handed to the next module) per table or field. Send them to a spreadsheet and you get up-to-date documentation of your Quickbase build, handy before a handover.

Settings that stay aligned. Get a Field shows how a column is configured and Update a Field corrects it, custom permissions included. Useful when several apps must follow the same rules.

What the list does not cover: Quickbase has no trigger in Make, so it never starts a scenario by itself, and every module targets apps, tables or fields. For anything else, Make an API Call reaches any endpoint of the Quickbase API with the same connection. The app also has an n8n node, described on the Quickbase n8n integration page, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Quickbase to Make?

  1. 01

    Add a Quickbase module

    Open your scenario, click the +, search for Quickbase and pick any module, Get an App for instance. Click Create a connection. A connection is your Quickbase account linked to Make once, then reused by all 15 modules.

  2. 02

    Copy a user token

    In Quickbase, click your name at the top right, open My Preferences, scroll to My User Information and click Manage my user tokens. Reuse an existing token or click + New user token, then copy it from the list.

  3. 03

    Paste it and save

    Back in Make, type a label in Connection name if you want, which helps once you manage several accounts. Paste the token, or follow the on-screen instructions, and save. The module can now list the Quickbase items your account reaches.

First scenario

Your first scenario: a Quickbase app for every signed project

GoalWhen a project is signed in your CRM, Make creates a Quickbase app and its first table.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the tool where projects start, your CRM for example. It will pass one bundle per signed project.

  2. 02

    Add Create an App

    Click the + on the right of the trigger, search Quickbase and choose Create an App. Select your connection, or click Create a connection if this is your first Quickbase module.

  3. 03

    Map the project data

    Fill the module with data from the trigger, such as the client or project name, so each new app is easy to recognize in Quickbase later on.

  4. 04

    Chain Create a Table

    Click the + again and add Create a Table. Map the app returned by Create an App instead of picking one from the list, so the table lands in the app you just made.

  5. 05

    Test with Run once

    Create a test project in your CRM, then click Run once. Open the bubble above each module to read the bundles it received, and check the new app in Quickbase.

  6. 06

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, the floor on the Free plan. Switch the scenario on. Each module run on a bundle counts as one operation.

Modules

What each Quickbase module does in Make

Quickbase gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Quickbase1

Create a Field

Action

In Make“Creates a field within a table, including the custom permissions of that field.”

Create a Field adds a new column to an existing Quickbase table and can set its custom permissions in the same step, so the right people see or edit it from the start.

When to use it
right after Create a Table, to give a fresh table the columns your team will fill in.
Watch out
the module creates one field per run, so chain it once for every column you need.
Quickbase2

Create an App

Action

In Make“Creates an application in an account.”

This module builds a brand new application in your Quickbase account: an empty container you then furnish with tables and fields through the modules that follow.

When to use it
a new client, site or project deserves its own space, and you want it set up the same way every time.
Watch out
test with Run once on a dummy record first, or you will have a stray app to clean up.
Quickbase3

Create a Table

Action

In Make“Creates a table in an application.”

Need a new list inside an app, like contacts, tasks or invoices? Create a Table adds it to the application you choose, ready to receive fields.

When to use it
after Create an App, or when a process gains a step that deserves its own table.
Watch out
map the app from the previous module rather than picking it by hand, otherwise every run writes into the same app.
Quickbase4

Delete an App

Action

In Make“Deletes an entire application, including all of the tables and data.”

Delete an App removes a whole application, with every table and every piece of data it holds. Nothing stays behind in Quickbase.

When to use it
clearing out test apps created while you built and tried a scenario, once you are sure nobody relies on them.
Watch out
a deletion cannot be undone. Try it on a throwaway app, and check twice which app the mapping points to.
Quickbase5

Delete a Table

Action

In Make“Deletes a specific table in an application, including all of the data within it.”

Where Delete an App wipes everything, Delete a Table is narrower: it drops a single table from an application, along with all the data stored in it.

When to use it
a temporary table, used for an import or a short project, has done its job.
Watch out
the data leaves with the table, so export what you want to keep before this module runs.
Quickbase6

Delete Fields

Action

In Make“Deletes one or many fields in a table, based on field ID(s).”

Delete Fields removes one or several columns from a table, identified by their field IDs. The plural in the name matters: a single run can clear many fields at once.

When to use it
tidying a table after a process change left columns that nobody fills anymore.
Watch out
run List Fields first to collect the right IDs, because a wrong ID removes the wrong column.
Quickbase7

Get a Field

Action

In Make“Gets the properties of an individual field, based on field ID.”

Get a Field returns the properties of one column, found by its field ID, so the next modules know exactly how it is configured.

When to use it
before Update a Field, to compare the current settings with the target and change only what differs.
Watch out
it expects the field ID, not the column label you see on screen; List Fields is the quickest way to find it.
Quickbase8

Get an App

Action

In Make“Returns the main properties of an application.”

Get an App reads the main properties of one Quickbase application and passes them along as a single bundle.

When to use it
a scenario must confirm an app exists, or copy its details into a report or a team message, before acting on it.
Watch out
it describes the app itself, not what sits inside; pair it with List Tables to see the tables.
Quickbase9

Get a Table

Action

In Make“Gets the properties of an individual table that is part of an application.”

Focused on one table, this module fetches its properties inside a given application, handy when a later step depends on how that table is set up.

When to use it
just before Update a Table, or to document a single table without listing the whole app.
Watch out
choose the app first; Make then offers the tables it contains, which avoids typing identifiers by hand.
Quickbase10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the escape hatch. It sends any request to the Quickbase API with the connection you already set up, so there is no second login to manage.

When to use it
the ready-made modules stop short of what you need, for example anything beyond apps, tables and fields.
Watch out
you write the request yourself, so keep the Quickbase API documentation open while you fill it in.
Quickbase11

Update a Field

Action

In Make“Updates the properties of a field, including the custom permissions.”

Update a Field changes the settings of a column that already exists, and that includes who can see or edit it through custom permissions.

When to use it
a rule changes, say a field must become read-only for one team, and you want the change applied across several tables.
Watch out
call Get a Field first, so you keep a trace of the starting point in case you need to revert by hand.
Quickbase12

Update an App

Action

In Make“Updates specific application.”

With Update an App, you change the properties of an application that already exists instead of rebuilding it from scratch.

When to use it
a project gets reorganized in another tool, and its Quickbase app should follow without anyone opening the builder.
Watch out
map the app from an earlier module, such as Get an App or Create an App, so the scenario edits the right one.
Quickbase13

Update a Table

Action

In Make“Updates the main properties of a specific table.”

Update a Table edits the main properties of one table, which spares you a trip to the Quickbase builder for a small correction.

When to use it
several apps built on the same pattern need the same table adjustment, and doing it app after app by hand invites mistakes.
Watch out
test on one app with Run once before letting the scenario touch the rest.
Quickbase14

List Fields

Search

In Make“Gets the properties for all fields in a specific table.”

List Fields returns every field of a chosen table with its properties. As a search module, it can bring back zero, one or many results, each one a separate bundle.

When to use it
documenting a table, or collecting the IDs that Get a Field, Update a Field and Delete Fields ask for.
Watch out
map the field ID into those modules, not the label, or they will not find the column.
Quickbase15

List Tables

Search

In Make“Gets a list of all the tables that exist in a specific application.”

Pick an application and List Tables brings back all the tables it contains, each one handed to the next module as its own bundle.

When to use it
building an inventory of a Quickbase app, or applying the same change to every table in it.
Watch out
the modules placed after it run once per table, so a large app multiplies the operations counted on your plan.
Need help

Need help automating Quickbase with Make?

A person reads every message.

FAQ

Quickbase and Make: common questions

01Is the Quickbase Make integration free to use?
Yes. Quickbase is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits (operations) per month. Your Quickbase subscription is separate: check the Quickbase pricing page for that side.
02What does it take to connect Quickbase to Make?
You need a provisioned Quickbase user account with a username, a password and an assigned Quickbase role. Then generate a user token: click your name at the top right of Quickbase, open your preferences and scroll to the user token management page, where you can reuse a token or create one. In Make, add any Quickbase module, click Create a connection, paste the token and save. That single connection serves all 15 Quickbase modules in every scenario you build.
03Can a change in Quickbase start a scenario?
Not directly. Quickbase has no trigger module in Make, so it cannot start a scenario on its own. You have two ways around it. Start the scenario with the trigger of another app, such as your CRM or a form tool, and place the Quickbase modules after it. Or run it on a schedule set on the first module: every 15 minutes by default, 15 minutes at the shortest on the Free plan and 1 minute on paid plans. Then use List Tables or Get an App to read what you need.
04What if the Quickbase module you need is missing?
Use Make an API Call. It calls any endpoint of the Quickbase API with the connection you already created, so you can reach what the 15 modules leave out, for instance anything beyond apps, tables and fields. You write the request yourself, which takes a little more care than filling a ready-made module. Also note that the Make documentation for this app carries a warning: it was generated from the official Quickbase documentation and may contain mistakes, so confirm important details with Quickbase directly.
05Make or n8n: which fits Quickbase better?
It depends on the tool your team already works in. Both connect to Quickbase: Make offers 15 ready modules focused on apps, tables and fields, plus Make an API Call for the rest, all in a visual editor where you test with Run once. n8n also has a Quickbase node, covered on its own page on this site. Compare the list of what each one covers against the tasks you plan to automate, then pick the platform where your other scenarios or workflows already run.
Same platform

Other docs you might need on this stack.

Browse all integrations