NocoDB
DatabaseConnect AI agents to NocoDB, the open-source no-code database. Agents read and write table records, manage linked records, provision tables, and inspect base and view metadata.
What This Integration Enables
Agents sync records between NocoDB and other apps, look up a single record by primary key or filter and page through large tables with NocoDB's where syntax, maintain relationships by listing, linking, and unlinking related records, provision tables with typed columns, and inspect base, table, field, and view metadata to drive dynamic automations. The where syntax builds conditions as `(field,operator,value)` combined with `~and` or `~or`, so an agent can express precise filters without hand-writing SQL.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Filtered change detection
On a schedule, the agent calls List Records with a where filter for new or changed rows, reads the matches, and notifies the team of anything that needs attention with Slack. Instead of pulling the whole table and diffing, the agent asks NocoDB for exactly the rows that matter.
Migrating and mirroring data
The agent reads rows from another source, for example an Airtable base, and calls Create Records to migrate or mirror them into a NocoDB table, or Update Records by primary key to keep the two in sync. Where the data model is relational, it uses Link Records to preserve the connections between tables.
Cleanup with a human gate
An agent is asked to remove stale records. Before it runs Delete Records above the configured threshold, it does not act on its own. It routes the primary keys and a count for approval, and deletes only after a person confirms.
Human-in-Loop Highlight
A batch Delete Records against a shared NocoDB table is easy to run and visible to everyone if it goes wrong. 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 remove more rows than the configured threshold, the agent pauses before executing and asks through Slack: "This Delete Records on `Orders` would remove 355 rows. Here is the key list and a sample. Approve, narrow the set, 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 Capabilities
15 actionsRecords
6- Count Records Returns the number of rows in a table matching an optional where filter.
- Create Records Creates one or more rows in a table.
- Delete Records Deletes rows by primary key.
- Get Record Fetches one row by primary key.
- List Records Reads rows with NocoDB where filter syntax, ordering, and pagination.
- Update Records Updates rows by primary key.
Linked Records
3- Link Records Links related rows across tables via a link field.
- List Linked Records Lists the rows linked to a row through a link field.
- Unlink Records Removes a link between related rows.
Bases & Tables
5- Create Table Creates a table with typed columns in a base.
- Get Base Returns the metadata of a base.
- Get Table Returns the metadata of a table.
- List Bases Lists the bases available to the token, for discovery.
- List Tables Lists the tables in a base.
Views
1- List Views Lists the views of a table.
Start building with NocoDB
$100 in credits. No card required. Connect in minutes.