---
title: "NocoDB Integration"
description: "Connect 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."
url: https://flowrunner.ai/integrations/nocodb
date_modified: 2026-08-01T02:40:32-07:00
---

# NocoDB

[Database](https://flowrunner.ai/integrations/category/databases-warehouses)

Connect 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.

[Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 15 actions · API key · available

[NocoDB website](https://nocodb.com/) · [Platform Documentation](https://docs.nocodb.com/) · Capability data verified 2026-07-14

1.  A scheduled flow needs to find and act on changed rows
2.  Agent runs List Records with a where filter for recently changed rows
3.  Agent reads the matching records
4.  Agent evaluates which records need a downstream action
5.  Agent runs Link Records to relate them to the right parent row
6.  Agent notifies the team of matching records via Slack
7.  Any Delete Records above a threshold pauses for approval

## 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

**Relationships by hand**: Linking related rows across tables is a manual chore

**Polling without filters**: Finding changed rows means reading everything and comparing

**Bulk deletes unguarded**: A batch delete can remove more records than intended

### With FlowRunner

**Automated linking**: Link and Unlink Records maintain relationships as a flow step

**Filtered reads**: List Records with a where filter returns only the rows that matter

**Guarded deletes**: Delete Records above a threshold pauses for human approval

## 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 processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

## Agent Capabilities

15 actions

### Records

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.

## Frequently Asked Questions

### What can FlowRunner do with NocoDB?

FlowRunner agents can run Count Records, Create Records, and Delete Records in NocoDB, plus 12 more actions.

### Does connecting NocoDB to FlowRunner require OAuth?

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

### Can NocoDB trigger a FlowRunner workflow automatically?

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

**Work at NocoDB?** This integration exposes NocoDB 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/nocodb. Site index: https://flowrunner.ai/llms.txt
