SeaTable
DatabaseConnect AI agents to a SeaTable base. Agents read, append, and update rows in bulk, run read-only SQL over base data, maintain row links, and discover table and column names.
What This Integration Enables
Agents sync records in bulk with Append Rows and Update Rows (up to 1000 per request), log form submissions and webhook payloads as new rows, query and aggregate base data on demand with read-only SQL, maintain relationships between tables with row links, and discover table and column names before performing data operations. Query with SQL runs read-only SELECT statements against base tables and converts result column keys to human-readable names, so the output is easy to route onward. Get Base Metadata resolves the table and column names an agent needs before it writes.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Bulk sync into a base
New records arrive, for example rows from a spreadsheet. The agent reads them and calls Append Rows to bulk-sync up to 1000 at a time, so a large import is a handful of requests rather than hundreds. The team's base stays current with the source system.
Report and write back
The agent calls Query with SQL to pull rows matching a condition, sends a digest to the team with Slack, then calls Update Row to record the outcome (for example a created reference in another tool) back on each matching row. Reporting and write-back happen in one flow.
Cleanup with a human gate
An agent is asked to purge rows. Before it runs Delete Rows above the configured threshold, it does not act on its own. It routes the affected rows and a count for approval and deletes only after a person confirms.
Human-in-Loop Highlight
Appends and updates in SeaTable are safe to repeat; a bulk Delete Rows is the one that removes data collaborators may still rely on. 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 Rows would remove more rows than the configured threshold, the agent pauses before executing and asks through Slack: "This Delete Rows on the `Projects` table would remove 180 rows. Here is 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 rows; an orchestration layer knows which deletes should stop and ask.
Agent Capabilities
13 actionsMetadata
1- Get Base Metadata Returns the tables and columns of the base, so an agent can resolve names before reading or writing.
Rows
8- List Rows Reads rows from a table, optionally through a view, with start and limit pagination up to 1000 rows.
- Get Row Fetches one row by id.
- Append Row Appends one row to a table, keyed by column name.
- Append Rows Appends many rows in one request (up to 1000), for bulk syncs.
- Update Row Updates one row by id.
- Update Rows Updates many rows in one request.
- Delete Row Deletes one row by id.
- Delete Rows Deletes many rows in one request.
SQL
1- Query with SQL Runs a read-only SELECT against base tables, with human-readable result column names.
Links
3- Add Link Links two rows across tables.
- List Row Links Lists the rows linked to a row.
- Remove Link Removes a link between two rows.
Start building with SeaTable
$100 in credits. No card required. Connect in minutes.