Baserow
Read, create, update, move and delete Baserow rows — singly or in batches of up to 200 — and browse the tables and fields a database token can reach.
About
Baserow ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.baserow- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Databases · Spreadsheets · Productivity
Overview
Baserow is an open-source, no-code database with the shape of a spreadsheet and the guarantees of a real database underneath, and this app is built around the part of it a workflow actually touches: rows. Read them with the same filters a saved view already applies, write them one at a time or two hundred at a time, and move or remove them without opening the grid.
Because Baserow runs equally as a hosted cloud product and as a container someone deployed themselves, this app works against either — the instance address travels with the credential rather than being hard-coded. Before writing, a workflow can browse what a database token can actually reach: which tables exist and what fields each one has, so a bulk import can be built against the real schema instead of a guess.
Schema changes — creating tables or fields, or building views — stay a task for Baserow’s own interface; this app is deliberately about moving data through an already-designed base, which is what a workflow needs it for.
Build with Baserow
Three routes to the same 12 actions. The Workflow tab is generated from Baserow's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Rows
row-list List a table's rows with optional search, filters, ordering and view scoping. Returns Baserow's `{count, next, previous, results}` envelope.
Get Row Names
row-names Resolve a list of row ids to their primary-field values in one request — the cheap way to turn link-row ids into names.
Update Row
row-update Update a row's fields. Omitted fields keep their value; send `null` to clear one.
Update Rows (Batch)
rows-update-batch Update up to 200 rows in one request. Every row object must include its `id`.
List Tables
table-list List every table this connection's token can reach, with its id and database id. Start here to find the Table ID the row actions need.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Baserow's real ids.
{
"manifestVersion": "2",
"name": "baserow-example",
"steps": [
{
"id": "field-list",
"uses": {
"app": "io.w6w.baserow",
"action": "field-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"tableId": "<tableId>"
}
}
]
}Here are some of the things you can do
-
List Fields
searchfield-list -
Create Row
performrow-create -
Get Row
readrow-get -
List Rows
searchrow-list -
Move Row
performrow-move
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Baserow, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Baserow. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "row-create",
payload: {
tableId: "<value>",
fields: "<value>",
// userFieldNames: "<value>",
// before: "<value>",
// view: "<value>",
// sendWebhookEvents: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action row-create --payload '{"tableId":"<value>","fields":"<value>"}'Give an AI agent Baserow — without giving it Baserow's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.baserow#field-list",
"input": {
"tableId": "<tableId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Baserow connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Baserow's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Baserow itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Baserow declares its own checks, so its health is a property of the app rather than something the host guesses at.
Baserow hosted status
Resource status from status.baserow.org (Better Stack). Covers Baserow's hosted service — a self-hosted instance is unaffected, which is why this check is informational and the per-connection credential check carries the weight.