NoCodeTable
DatabaseNoCodeTable is a hosted spreadsheet-database with documents, tables, fields, views and records. Agents create and query records, manage tables, fields and views, validate formula fields and set document, table and record configuration.
What This Integration Enables
NoCodeTable is a hosted spreadsheet-database in the Airtable mould: documents hold tables, tables hold fields, views and records. What makes it worth a page of its own is where the vendor drew its lines. It ships a rehearsal for a formula, so Validate Formula Field returns a sample record showing what an expression would produce before the column exists. It ships no rehearsal at all for a wholesale record replacement, and no soft delete anywhere: deleting a document takes its tables and records with it, permanently. The product also runs as two separate regional deployments rather than as mirrors, which makes data residency a connection setting rather than a negotiation.
FlowRunner agents work the full surface: creating documents with their tables, adding and renaming fields, saving views so the filter a workflow uses is the same one people see, counting a table or a view before paging it, and reading and writing records with structured filters. They also read and write the presentation settings the product stores, so a table an agent provisions arrives with the right primary column and the right things hidden.
Two writes sit side by side in this API and behave very differently, which is precisely the kind of place human-in-the-loop belongs: not on everything, but on the one call whose consequence is invisible until afterward.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A document provisioned per engagement, complete on arrival
When a new client engagement opens, the agent calls Create Document with every table the engagement needs supplied in the same call, because tables cannot be added as a separate step of that request. It then adds any extra columns with Create Field, saves the team's working filters with Create View, and uses Set Field Config to make the right column primary and hide the internal ones. The kickoff rows land through Create Records. The workspace looks the same for the tenth client as it did for the first, and nobody assembled it.
-
Reporting where the flow and the team see the same rows
Rather than expressing a filter only inside the workflow, the agent calls Create View so the filter is stored in the product. Get View Record Count then reports the size of that subset without fetching it, and List Records pages through it with the cursor rather than an offset, because offset paging drifts when records are inserted mid-sweep. The numbers post to Slack and append to a sheet in Google Sheets. When someone questions a figure, they open the same view the agent read.
-
A re-import that respects what people typed
The customer master is re-imported nightly from an upstream system. Replace Record is the technically correct write for that, because a re-import should clear values the source no longer carries. But the table also holds a notes column that only humans ever fill. The agent diffs each incoming row against the current record, separates the fields the export owns from the fields it does not, and uses Update Record wherever a targeted write is enough. What is left goes to a person before anything is replaced.
Human-in-Loop Highlight
NoCodeTable exposes both an edit and a replacement on a record and names them honestly: Update Record writes only the fields supplied, while Replace Record clears every field it is not given. The vendor's own description of the second is a destructive update. Notice what is not in the API alongside it. There is a preview for a formula column, and there is no preview, no dry run and no undo for a record replacement, and no trash to recover from. So the re-import agent treats the replace as a decision rather than a write. It posts: "The nightly export covers 9 of the 14 columns on Customers. Replacing 312 records would clear values in 5 columns the export does not carry, including Account Notes, which currently holds text on 87 of those records and was last edited in the product rather than by this flow. Replace anyway, restrict the write to the 9 export columns, or hold?" A data owner answers. If the answer is to restrict, the agent falls back to targeted writes and nothing is lost. The agent did the diff across every column and every row. Whether a column of human-written notes counts as stale data was never a question the agent could answer.
Agent Capabilities
33 actionsDocuments
5- List Documents Lists the documents the API key can reach, in the order they appear on the home screen, continuing through a cursor when more remain.
- Create Document Creates a document together with its tables and returns the schema of what was created. Tables cannot be added in a separate step of the same call, so supply every table the document should start with.
- Get Document Returns a single document by identifier or by name, with its schema key, display name, color and last touched time.
- Update Document Renames a document. The document level exposes only the name, so everything inside it changes through the table, field and view operations.
- Delete Document Permanently deletes a document and all of its tables and records. There is no undo and no soft delete.
Tables
6- List Tables Returns the schema of every table in a document with full column definitions. Used to discover field identifiers before reading or writing records.
- Create Table Creates a table in a document with the columns specified and returns the schema of what was created.
- Get Table Returns the schema of a single table, with every column's identifier, name, type and options. The call to make before mapping flow data onto record fields.
- Update Table Renames a table or changes its description. At least one of the two has to be supplied.
- Delete Table Permanently deletes a table and every record in it. There is no undo.
- Get Table Record Count Returns how many records a table holds, optionally counting only those matching a filter. Used to size a job before paging.
Fields
4- Create Field Adds a column to a table and returns the schema of the new column. Simple types are named directly, and richer types carry their options alongside.
- Update Field Renames a column or changes its description.
- Delete Field Permanently deletes a column along with the values every record holds in it. There is no undo.
- Validate Formula Field Checks whether a formula column definition is valid without creating it, and returns a sample record showing what the formula would produce. The rehearsal that catches a bad formula before it reaches a table with data in it.
Views
6- List Views Returns every view defined on a table with its sort field, direction and filter set. How a workflow discovers the filters already configured in the product.
- Create View Creates a saved view on a table. Creating a view stores the filter in the product, so people looking at the table see the same subset a flow does.
- Get View Returns a single view with its name, sort settings and the full structured filter it applies.
- Update View Updates a view's name, sort field, direction or filter.
- Delete View Deletes a saved view. The records are untouched, because a view is only a way of looking at them.
- Get View Record Count Returns how many records fall inside a view with its own filter applied. Used to check the size of a filtered set without fetching it.
Records
6- List Records Lists records in a table with sorting, paging and structured filtering. Both a cursor and an offset are accepted, and the cursor is the one to prefer for a full sweep because offset paging drifts when records are inserted mid-read.
- Create Records Creates one or more records in a single call and returns them with the identifiers and creation times NoCodeTable assigned.
- Get Record Returns a single record by identifier with its creation time and every field value.
- Update Record Updates only the fields supplied and leaves every other cell untouched. The safe update and the default choice.
- Replace Record Replaces a record wholesale: every field not supplied is cleared. Reach for it only when the unlisted cells genuinely should be emptied, such as a re-import from an authoritative source.
- Delete Record Permanently deletes a single record. There is no undo.
Configuration
6- Get Table Config Reads one of a table's stored layout settings, such as column widths, row order or which columns are hidden.
- Set Table Config Writes one of a table's stored layout settings, so a provisioned table arrives looking the way the team expects.
- Get Field Config Reads one of a field's stored presentation settings, such as whether it is the primary column, whether it is hidden, its width or its position.
- Set Field Config Writes one of a field's stored presentation settings, such as making it the primary column or hiding it from the grid.
- Get Record Config Reads a per record stored setting. These are presentation state rather than record data.
- Set Record Config Writes a per record stored setting, using one of the config keys NoCodeTable publishes for records.
Frequently Asked Questions
What can FlowRunner do with NoCodeTable?
FlowRunner agents can run List Documents, Create Document, and Get Document in NoCodeTable, plus 30 more actions.
Does connecting NoCodeTable to FlowRunner require OAuth?
No. NoCodeTable connects to FlowRunner with an API key, no OAuth flow required.
Can NoCodeTable trigger a FlowRunner workflow automatically?
NoCodeTable doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Database integrations
Start building with NoCodeTable
Free plan, no card required. Connect in minutes.