QuintaDB

QuintaDB is an online database and form builder where databases hold forms, fields and records, with saved reports as filtered views. Agents create and update databases and forms, search and write records, update cells in bulk, upload files and run configured actions.

37 actions API key available

QuintaDB website Platform Documentation Capability data verified 2026-08-27

A scheduled sweep runs against the applications form

List Fields resolves the field identifiers the form's values are keyed by

Search Records finds submissions still sitting in the unreviewed state

Get Column Total reports the committed amount across the matched set without reading every record

Update Multiple Records advances only the named submissions to the reviewed state

The agent posts the batch and its total to the reviewer

The reviewer confirms the set before any status change reaches the whole form

What This Integration Enables

QuintaDB is a form builder with a real database underneath, and the two are the same object rather than two systems wired together. A database holds forms, a form holds fields and records, and saved reports are filtered views over a form. That collapses a gap most intake stacks never close: the thing the public fills in and the thing operations reports on are one record, so an agent that writes to a form is writing to the system of record, not to a staging copy of it.

FlowRunner agents work at every level of that hierarchy. They create databases and forms, add and change fields, read and write records, upload files, and run the same action buttons a person clicks in the interface. Two details shape how a flow is built here. Record values are keyed by field identifier rather than by field name, so List Fields comes before any write; and linking records uses a relationship identifier that is a different value from the field identifier, which is what Get Relationship ID exists to resolve. The connectors handle that resolution so a flow does not have to carry a hand-maintained map of identifiers that goes stale the first time someone adds a column.

Without FlowRunner

The form and the table drift Intake lives in one tool and the records it produces live in another, and the two stop agreeing

Bulk edits are all or nothing Changing a status across a batch means exporting, editing, and re-importing, or clicking through records one at a time

Field names are a guessing game Values are keyed by internal identifier, so a hand-built payload writes to the wrong column and reports success

With FlowRunner

One object, two faces Agents read and write the same form the public submits to, so intake and record keeping never diverge

Scoped batches Search Records defines the set, Update Multiple Records changes exactly that set, and the unscoped variant stays behind a person

Identifiers resolved at run time List Fields and Get Relationship ID turn the labels a team uses into the keys a write needs

Use Case Scenarios

Applications that route themselves

A public form collects applications. On each sweep the agent calls Search Records for submissions in the unreviewed state, reads each one, and classifies it. Clean submissions get Update Record to advance the status and a summary posts to Slack for the owning team. Submissions missing a document get an email through Gmail naming exactly what is absent, and the record stays where it is. Nothing is deleted, nothing is guessed, and the queue shrinks to the applications that genuinely need a decision.
Files that arrive attached, not orphaned

QuintaDB requires the file before the record: a file cannot be attached to a record the database has not seen. So the agent generates the record identifier itself, calls Upload File with that identifier, then calls Create Record passing the same value. The document and the record are bound from the first moment they exist. A later flow can hand the reader a working link with Get File URL, which the agent assembles from the record's own values because QuintaDB publishes no endpoint for it.
A reconciliation that adds up on the server

Finance needs the committed total on an open form each week. Rather than pulling every record into the flow to sum a column, the agent calls Get Column Total against a saved report, which applies that report's own filters and sorting. The figure goes into a sheet in Google Sheets alongside the same period pulled from Stripe, and the difference between the two is the only thing a person has to look at.

Human-in-Loop Highlight

The dangerous operation on this API is not named like one. Update All Records applies the same change to every record in a form, with no filter and no confirmation step, and it succeeds quietly. It sits in the action list one line below Update Multiple Records, which does the same thing to a named set, and the only difference between correcting forty records and overwriting forty thousand is which of the two the flow calls. So a FlowRunner agent building a bulk correction never calls the unscoped one on its own. It runs Search Records with the intended condition, reports the matched count and the exact values it would write, and asks: "This changes the Status field to Closed on 412 records matched by the filter. Update Multiple Records will change those 412. Update All Records would change all 8,930 records in the form. Confirm the scoped write, or tell me the whole form is intended?" A person answers before anything is written. The same rule covers Delete All Records, Delete Form, and Delete Database, which takes its forms and their records with it. The agent's job is to define the set precisely. Deciding that the set is genuinely everything is a person's job.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

37 actions

Databases

List Databases Lists the databases on the account, twenty per page. A database holds forms and forms hold records, so this is the top of the hierarchy every other operation descends from.
Get Database Reads one database by identifier, including its form, column, and record counts and whether data caching is enabled.
Get Database By Name Finds a database by name rather than identifier, which saves listing everything when a flow only knows what the database is called.
Create Database Creates a database together with its first form. QuintaDB does not allow an empty database, so the form name is part of this call rather than a separate step.
Update Database Renames a database.
Delete Database Permanently removes a database and everything inside it, forms and records included.

Forms

List Forms Lists the forms in a database. QuintaDB calls a form an entity in its URLs, and a form is what other tools call a table.
Get Form Reads one form by identifier.
Get Form By Name Finds a form by its name and the name of the database holding it, so neither identifier has to be known in advance.
Create Form Adds a form to an existing database.
Update Form Renames a form.
Delete Form Permanently removes a form and every record in it.

Fields

List Fields Lists a form's fields with their identifiers. Record values are keyed by identifier rather than by name, so this is the call that makes a write possible.
Get Field Reads one field's definition and settings.
Get Field By Name Finds a field by name, given the names of the database and form holding it, so no identifier has to be known in advance.
Create Field Adds a field to a form.
Update Field Changes a field's name or settings.
Delete Field Permanently removes a field and the data held in it across every record.
Get Column Total Sums a numeric column across a form, or across one report of it, without reading the records.

Records

List Records Reads records from a form, optionally through a saved report. The maximum page size is set by the account's plan, and asking for more than the plan allows is capped rather than refused.
Get Record Reads one record by identifier.
Create Record Adds a record to a form, with values keyed by field identifier. To attach a file, supply the Record ID yourself and upload the file first, because QuintaDB cannot attach a file to a record that does not yet exist.
Update Record Changes the named values on one record and leaves the rest untouched.
Update Cell Writes a single cell, which is cheaper than sending a whole record when only one value changes.
Update Multiple Records Applies the same change to a named set of records in one call. The scoped bulk write, and the one an agent should reach for.
Update All Records Applies the same change to every record in a form. There is no filter and no confirmation step, which is why this page's human gate sits here.
Delete Record Permanently removes one record.
Delete Multiple Records Permanently removes a named set of records in one call.
Delete All Records Permanently removes every record in a form, leaving the form and its fields in place. There is no filter and no undo.
Search Records Finds records matching one or more conditions. Entries inside the same group combine with AND, and the groups themselves combine with OR.

Reports

List Reports Lists a form's saved reports. A report identifier can be passed to List Records, Search Records, and Get Column Total to apply that report's own filters and sorting.

Relationships

Get Relationship ID Reads the relationship identifier behind a link field. That identifier, not the field identifier, is the key a record write uses to link records together, and the two are different values.

Files

Upload File Uploads a file into a file field on a record. The upload has to happen before the record is created, which means the record identifier is chosen by the caller rather than generated by QuintaDB.
Delete File Removes the file held in a record's file field.
Get File URL Builds the download URL for a file held in a record. QuintaDB publishes no endpoint for this, so the URL is assembled from the record's own values, which means the record has to be read first.

Actions

Run Action Runs an action button field against one record, the same as a user clicking it in the interface.
Run Action On Multiple Records Runs an action button field against several records at once, or against every record in a form or report.

Frequently Asked Questions

What can FlowRunner do with QuintaDB?

FlowRunner agents can run List Databases, Get Database, and Get Database By Name in QuintaDB, plus 34 more actions.

Does connecting QuintaDB to FlowRunner require OAuth?

No. QuintaDB connects to FlowRunner with an API key, no OAuth flow required.

Can QuintaDB trigger a FlowRunner workflow automatically?

QuintaDB doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with QuintaDB

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us