Automate Quick Base With n8n: 10 Operations, 4 Resources

Why automate

What does the Quick Base n8n integration actually cover?

The Quick Base node ships with n8n and talks to the Quick Base RESTful API. Pick a resource in the first dropdown, Record, Field, File or Report, then pick one of the 10 operations behind it. Each call works against a single table, which is why Table ID appears in all of them, and the node reuses one credential you set up once.

Take a maintenance company whose work orders live in Quick Base. A Schedule Trigger fires at six in the morning, record.getAll pulls the open ones with a Where filter written in the Quick Base query language, and the list lands in Slack before the crews get in their vans. Nobody opens the app to build that list by hand anymore.

Second pattern: an intake form on a public site. The form posts to an n8n Webhook, which is a URL n8n exposes so another service can push data into a workflow, and record.upsert writes the request into the table. Because upsert matches on a merge field, a customer who submits the same request twice updates one row instead of creating a duplicate.

Third pattern is about files and reporting. file.download pulls an attachment out of a record into the workflow as binary data, ready to drop into Google Drive for long term storage. On the analytics side, report.run feeds an existing Quick Base report into a table in Postgres, so a BI tool reads numbers that were already validated by the people who built the report.

When what you need sits outside those 10 operations, the HTTP Request node calls any endpoint of the Quick Base API and reuses the same credential through predefined authentication. Same token, same hostname, no second setup. Keep an eye on volume too: with Return All off, Limit decides how many items come back, and a workflow that quietly reads a partial table is worse than one that fails loudly.

If you are still comparing platforms before you build, the n8n review goes through hosting and pricing models, and n8n training covers expressions and error handling, which is most of what makes a Quick Base workflow survive its second month.

Connect

How do you authenticate the node against your Quick Base app?

01
Generate a user token
Quick Base authenticates the node with an API key, and that key is a user token tied to your own account. In Quick Base, open Profile, then My preferences, then My User Information, then Manage my user tokens. Generate the token there and copy it before you leave the screen. The workflow acts through that token, so it reaches the apps that account reaches.
02
Read your hostname off the URL
The second value the credential wants is a Hostname, and it is already sitting in your browser. Open any table in Quick Base and look at the address: the hostname is the string between https:// and /db. Nothing before it, nothing after it. Copy that exact string, because it is what points the node at your realm rather than someone else's.
03
Save the credential once in n8n
In n8n, go to the Credentials menu and create a Quick Base credential, which is the stored pair of hostname and user token that nodes borrow at runtime. Paste both values, save, and every Quick Base node in every workflow can select it from a dropdown. You never retype the token: one credential serves the whole instance, on n8n Cloud or on a self-hosted install.

Actions

The 10 operations, one by one

The Quick Base node exposes 10 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Get	Get Many	Update	Delete	Download	Run	Create or Update
Field			✓
File					✓	✓
Record	✓		✓	✓	✓			✓
Report		✓					✓

Field

1 operation

01

Get many fields

field.getAll

What you see in n8n

Notes & use cases

Reads the field definitions of one table and passes them to the next node, so a workflow knows what it is allowed to write before it writes anything.

Key parameters

Table ID: the table identifier, typed in or taken from an earlier node with {{ $json.field }}.
Return All: on, n8n walks the pages of the API until the field list is complete; off, Limit sets the maximum number of fields returned.
Include Field Perms: on, the response also carries the custom permissions of the fields.

Use cases

match a spreadsheet header row against the real fields of a project table before a first import, instead of guessing the Columns value later.

File

2 operations

02

Delete a file

file.delete

What you see in n8n

Notes & use cases

Targets one version of a file attachment inside a record and deletes it.

Key parameters

Table ID: the table identifier the record belongs to.
Record ID: the unique identifier of the record holding the attachment.
Field ID: the unique identifier of the field, since a record can carry several attachment fields.
Version Number: the file attachment version number, so a specific upload is removed rather than whatever is most recent.

Use cases

a contractor uploads a corrected drawing, and the workflow clears the superseded version from the equipment record once the new one is registered.

03

Download a file

file.download

What you see in n8n

Notes & use cases

Fetches an attachment out of a record and carries it into the workflow as binary data the following nodes can store or send.

Key parameters

Table ID, Record ID and Field ID: the table identifier, the unique identifier of the record, and the unique identifier of the attachment field.
Version Number: the file attachment version number you want.
Input Binary Field: the name of the input binary field containing the file to be written.

Use cases

pull every signed inspection sheet from last week into a cloud folder, so auditors stop asking for exports one record at a time.

Record

5 operations

04

Create a record

record.create

What you see in n8n

Notes & use cases

Writes a new row into a Quick Base table from the data flowing through the workflow.

Key parameters

Table ID: the table identifier that receives the row.
Columns: a comma separated list of the properties used as columns for the new rows.
Simplify: on, the node returns a simplified version of the response instead of the raw data.
Return Field Names or IDs: the field IDs to return for the added record; ask for any of them and Record ID, FID 3, comes back too.
Use Field IDs: on, Columns is read as field IDs rather than field names.

Use cases

each equipment delivered on site becomes a row in the asset table.

05

Create or update a record

record.upsert

What you see in n8n

Notes & use cases

One call that creates the row, or updates the existing one when it is already there, which is what you want for any feed that can repeat itself.

Key parameters

Table ID and Columns: the destination table identifier and the comma separated list of properties used as columns.
Update Key: the key field on the table, or any other supported unique field.
Merge Field Name or ID: the field holding the unique values Quick Base matches on, so source data finds its counterpart in the destination table.
Simplify: returns a simplified response rather than the raw payload.

Use cases

a nightly supplier feed refreshes contract rows without ever duplicating a supplier.

06

Delete a record

record.delete

What you see in n8n

Notes & use cases

Deletes the rows that match a filter, which makes it the most destructive operation in the node and the one to test on a copy first.

Key parameters

Table ID: the table identifier to clean up.
Where: the filter that selects what gets deleted. To wipe everything you write a filter that includes all records, for example {3.GT.0} where 3 is the ID of the Record ID field.

Use cases

a staging table gets emptied at the end of a migration run, once the rows have been confirmed on the production side.

07

Get many records

record.getAll

What you see in n8n

Notes & use cases

Queries a table and returns the matching rows to the workflow, which is the starting point of most exports and recaps.

Key parameters

Table ID: the table identifier being queried.
Return All: on, n8n chains the API pages until everything is in; off, Limit caps the number of rows.
Select: an array of field IDs to return; left empty, the default columns of the table come back.
Where: the filter, written in the Quick Base query language, that decides which records are returned.
Sort By: queries are sorted by the given sort fields by default; skipping the sort when order does not matter can improve performance.

Use cases

send the morning list of open work orders to the team channel.

08

Update a record

record.update

What you see in n8n

Notes & use cases

Changes values on rows that already exist, leaving the columns you do not mention untouched.

Key parameters

Table ID: the table identifier holding the rows.
Columns: the comma separated list of properties used as columns for the rows being written.
Update Key: the key field on the table, or any other supported unique field, so the node knows which row each item belongs to.
Use Field IDs: on, Columns is interpreted as field IDs instead of field names.
Field Names or IDs: the array of field IDs returned for the updated record.

Use cases

a technician closes a job in the mobile app and the status column follows in Quick Base.

Report

2 operations

09

Get a report

report.get

What you see in n8n

Notes & use cases

Retrieves a report that already exists in the table, identified by its own report identifier.

Key parameters

Table ID: the table identifier the report was built on.
Report ID: the identifier of the report, unique to the table, so two tables can each have a report numbered the same way without any clash.

Use cases

a workflow that documents itself, reading the report reference before it runs anything, so the run log says exactly which saved report the numbers came from.

10

Run a report

report.run

What you see in n8n

Notes & use cases

Executes a saved report and brings its results into the workflow, filters and column choices already applied by whoever built it.

Key parameters

Table ID and Report ID: the table identifier, and the identifier of the report, unique to that table.
Return All: on, every page of results is retrieved; off, Limit fixes the maximum number of items returned.

Use cases

the finance team keeps its month end report in Quick Base, and the workflow pushes the same rows into the warehouse every night without rebuilding the logic.

Need help

Need help automating Quick Base with n8n?

A person reads every message.

FAQ

Questions people ask next

01Is the Quick Base n8n integration free to use?

Yes on the n8n side. The Quick Base node ships with n8n, so there is nothing to install and nothing extra to pay to unlock the 10 operations. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. The workflow you build is the same in both cases, which means you can prototype on Cloud and move it to your own server later. What a Quick Base plan costs on its side is a separate question, and this page does not answer it.

02What credentials does the Quick Base node need?

One credential, using the API key method, built from two values. The Hostname is the string between https:// and /db in your Quick Base URL. The User Token is generated from the user tokens screen of your Quick Base profile preferences, and the exact click path sits in the connection steps above. You create the credential once from the Credentials menu in n8n and every Quick Base node offers it in a dropdown afterwards, across all your workflows. Since the token belongs to a user account, the workflow works on the same apps and tables that account works on, which is worth checking before you hand a workflow to someone else.

03What are the limits of the Quick Base node?

Two things to keep in mind. First, volume: leave Return All off and Limit decides how many items come back, on records, fields and report results alike, so a long export needs Return All on if you want the full set rather than a first slice. Second, scope: the node covers 10 operations over 4 resources, and anything else you need from the Quick Base API goes through the HTTP Request node, which calls any endpoint and reuses the exact same credential through predefined authentication. No second token, no second hostname.

04Does Quick Base have a trigger node in n8n?

No, there is no Quick Base trigger node, so a workflow around it starts somewhere else. Three ways to do that. A Schedule Trigger runs your workflow at a fixed interval, then Get many records with a Where filter picks up what changed since the last pass. An n8n Webhook, meaning a URL n8n exposes that another service calls, lets a form or an external app push data in the moment it happens. Or another tool's trigger opens the workflow, and the Quick Base node simply acts as the destination for the data.

05n8n or Make for Quick Base?

It depends on where you want the automation to live. Make is hosted by Make, with no self-hosting option, and it bills per operation, so a workflow that reads a lot of records has a cost that follows its volume. n8n runs on n8n Cloud or on your own server, which matters when the data in your tables cannot leave a given infrastructure. Both give you a visual canvas. The honest test: sketch the same Quick Base workflow in each, look at how you handle errors and expressions, and pick the one your team will still understand in a year.

Generate a user token

Read your hostname off the URL

Save the credential once in n8n

Need help automating Quick Base with n8n?