Quickbase
Query, upsert and delete Quickbase records; manage tables, fields, relationships and reports.
About
Quickbase ships in the w6w first-party pack. It declares 20 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.quickbase- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Databases · Productivity · Project Management
Overview
Quickbase is a low-code application platform built around custom tables and records, and this app queries, updates and manages that data through Quickbase’s modern JSON REST API.
Record actions cover the core data loop: querying with Quickbase’s own filter language, inserting or updating records in bulk while reporting exactly which rows succeeded and which didn’t (a partial write still counts as an overall success), deleting by filter, and pulling only what has changed since a given time. Schema actions let a workflow read and manage the tables, fields and relationships records live in, and reporting actions list, read and run a Quickbase report to reuse work already built in the app. A formula action evaluates a Quickbase formula on demand without having to store it as a report first.
Records come back keyed by numeric field id rather than by field name, so this app also exposes field listings as the way a workflow discovers what each id actually means. Health checks track Quickbase’s own status page, live credential validity tied to a specific application, and API rate-limit headroom where Quickbase’s response headers make it available.
Build with Quickbase
Three routes to the same 20 actions. The Workflow tab is generated from Quickbase's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Fields
delete-fields Delete one or more fields from a table, with their data. Check `errors` — a 200 can still leave some fields undeleted.
Delete Records
delete-records Delete records matching a Quickbase query, or a list of record IDs. Requires an explicit filter.
Get Application
get-app Get an application's properties, including its application variables and security settings.
List Fields
list-fields List every field in a table, with its ID, label and type — the map from field names to the IDs the record actions use.
List Relationships
list-relationships List a table's relationships — parent table, foreign key, and the lookup and summary fields derived across them.
List Reports
list-reports List the saved reports on a table, with their filters and column definitions.
Query Records
query-records Query records from a table with the Quickbase query language. Returns one page — advance `skip` by the returned `numRecords` to page through.
Records Modified Since
records-modified-since List record changes — including deletions — in a table since a timestamp. The basis for an incremental sync.
Run Formula
run-formula Evaluate a Quickbase formula against a record without needing a formula field. Result is always a string.
Run Report
run-report Run a saved report and return its data. Shape follows the report type — record-level reports return rows, summary reports return aggregates.
Update Field
update-field Update a field's label, help text or settings. Unset fields are left alone.
Update Table
update-table Update a table's name, description or record nouns. Unset fields are left alone.
Insert or Update Records
upsert-records Insert and/or update records in one call. Rows carrying the key field update; rows without it insert. Reports per-row failures via `partialFailure`.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Quickbase's real ids.
{
"manifestVersion": "2",
"name": "quickbase-example",
"steps": [
{
"id": "create-field",
"uses": {
"app": "io.w6w.quickbase",
"action": "create-field",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"tableId": "<tableId>",
"label": "<label>",
"fieldType": "<fieldType>"
}
}
]
}Here are some of the things you can do
-
Create Field
performcreate-field -
Create Table
performcreate-table -
Get Application
readget-app -
Get Field
readget-field -
Get Report
readget-report
+15 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Quickbase, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Quickbase. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "upsert-records",
payload: {
tableId: "<value>",
data: "<value>",
// mergeFieldId: "<value>",
// fieldsToReturn: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action upsert-records --payload '{"tableId":"<value>","data":"<value>"}'Give an AI agent Quickbase — without giving it Quickbase's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.quickbase#create-field",
"input": {
"tableId": "<tableId>",
"label": "<label>",
"fieldType": "<fieldType>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Quickbase connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Quickbase's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Quickbase itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Quickbase declares its own checks, so its health is a property of the app rather than something the host guesses at.
Quickbase platform status
StatusCast rollup for Quickbase, read from quickbasestatus.status.page/status.json. Unauthenticated and unsigned.
API rate-limit headroom
Per-user-token allowance remaining, read off the `x-ratelimit-*` response headers. Quickbase documents 100 calls per 10 seconds per token.