--- title: "Quick Base Integration" description: "Connect AI agents to Quick Base through the JSON REST API. Agents query, insert, update, and delete records, manage tables and fields, run reports, and download file attachments." url: https://flowrunner.ai/integrations/quickbase date_modified: 2026-08-01T02:40:32-07:00 --- # Quick Base [Database](https://flowrunner.ai/integrations/category/databases-warehouses) Connect AI agents to Quick Base through the JSON REST API. Agents query, insert, update, and delete records, manage tables and fields, run reports, and download file attachments. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 16 actions · API key · available [Quick Base website](https://quickbase.com/) · [Platform Documentation](https://developer.quickbase.com/) · Capability data verified 2026-08-12 1. A scheduled flow needs to act on records matching a condition 2. Agent runs Query Records with a fid-based where clause 3. Agent reads the fid-keyed data, optionally mapping field labels for readability 4. Agent identifies the records that need an update 5. Agent runs Insert/Update Records to upsert the changes on the merge field 6. Agent alerts the team of the affected Record ID# via Slack 7. Any Delete Records or Delete Table against a production app pauses for approval ## What This Integration Enables Agents query records with a fid-based select and where clause, insert or update records with upsert on a merge field, delete records by a where clause, manage tables and fields, read app and report metadata, run saved reports, and download file attachments into FlowRunner storage. The Quick Base query language expresses conditions as `{fid.OPERATOR.'value'}` combined with uppercase `AND` and `OR`, and Record ID# is always fid 3. Query Records can return a `fieldLabels` map alongside the fid-keyed data, so an agent can produce readable output for a downstream step. ### Without FlowRunner **Fid guesswork**: Writing records means hand-tracking numeric field ids **Reports run in the app**: Someone opens Quick Base to run a report and read the numbers **Deletes without review**: A where-clause delete can remove more records than intended ### With FlowRunner **Governed record ops**: Query and Insert/Update Records run as named flow steps **Reports in the flow**: Run Report pulls a saved report's rows into the workflow **Guarded destructive ops**: Delete Records and Delete Table pause for human approval ## Use Case Scenarios ### Condition-driven updates On a schedule, the agent runs Query Records with a where clause such as `{6.CT.'urgent'}` to pull the records that match, reads the fid-keyed data (mapping field labels for readability), then runs Insert/Update Records to upsert the changes keyed on the merge field id. The app stays current without anyone working the grid by hand. ### Reporting and attachments The agent calls Run Report to pull a saved report's rows into the flow, then mirrors the data into a reporting spreadsheet. When a record carries a file, it calls Download File to decode the attachment into FlowRunner storage and pass the URL onward. The app's data and files move to where the rest of the workflow needs them. ### Cleanup with a human gate An agent is asked to remove records or a table from a production app. Before it runs Delete Records or Delete Table, it does not act on its own. It routes the where clause or table name and a matched count for approval, and proceeds only after a person confirms. ## Human-in-Loop Highlight A Delete Records with a broad where clause (for example `{3.GT.'0'}`, which matches every record in a table) or a Delete Table both remove data from a live app with no undo. FlowRunner's answer is human-in-the-loop, an execution pattern where the agent pauses on its own, assembles the context and the choices, routes to a human on their preferred channel, and resumes the moment they respond. When a Delete Records would match more records than the configured threshold, or a flow reaches Delete Table against a production app, the agent pauses before executing and asks through Slack: "This Delete Records on table `Tasks` matches 1,204 records with the where clause shown. Approve, narrow the clause, or cancel?" The delete runs only after a person confirms, with the approver and timestamp captured in the run log. A connector can delete any records; an orchestration layer knows which deletes should stop and ask. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 16 actions ### Records 3 - **Query Records** Queries records with a fid-based select and where clause in the Quick Base query language, optionally mapping field labels back for readability. - **Insert/Update Records** Inserts or updates records keyed by numeric field ids, upserting on a merge field id (Record ID# by default). - **Delete Records** Deletes records matching a where clause in the Quick Base query language. ### Tables 5 - **List Tables** Lists the tables in an app. - **Get Table** Returns the metadata of one table. - **Create Table** Creates a table in an app. - **Update Table** Updates a table's properties. - **Delete Table** Permanently deletes a table. ### Fields 4 - **List Fields** Lists a table's fields with their labels and numeric field ids. - **Get Field** Returns the definition of one field. - **Create Field** Creates a field on a table. - **Delete Fields** Deletes one or more fields from a table. ### Apps 1 - **Get App** Returns app metadata for a given application id (dbid). ### Reports 2 - **List Reports** Lists the reports defined on a table. - **Run Report** Runs a saved report and returns its rows. ### Files 1 - **Download File** Decodes a File Attachment field's contents and stores them in FlowRunner file storage, returning a URL. ## Frequently Asked Questions ### What can FlowRunner do with Quick Base? FlowRunner agents can run Query Records, Insert/Update Records, and Delete Records in Quick Base, plus 13 more actions. ### Does connecting Quick Base to FlowRunner require OAuth? No. Quick Base connects to FlowRunner with an API key, no OAuth flow required. ### Can Quick Base trigger a FlowRunner workflow automatically? Quick Base doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Quick Base?** This integration exposes Quick Base to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/quickbase. Site index: https://flowrunner.ai/llms.txt