Knack
Read, create, update and delete records in a Knack app's tables over its object-based REST API.
About
Knack ships in the w6w first-party pack. It declares 5 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.knack- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Databases · Productivity
Overview
Knack is a no-code database and app builder: every customer builds their own schema of Objects (tables) and Fields inside their own Knack application, then Knack generates a REST API over exactly that schema. This app is built around the one surface every Knack app shares regardless of what its builder designed — object-based record CRUD — because nothing else about a Knack app’s API is fixed in advance.
Each action takes the target Object’s key (object_1, object_2, …) as a parameter, since a single Connection’s credential can reach every table in the app, not just one. List records with Knack’s own filter/sort/pagination query language, fetch one by its record ID, and create, update or delete records by posting the field values your Knack app defines (field_1, field_2, …).
Knack’s REST API publishes no schema-discovery endpoint and no generic whoami: every authenticated route, without exception, is scoped to an Object or a View. That shapes two things worth knowing before connecting — a Connection needs one real Object key up front just to verify the credential is live, and finding your app’s Object and Field keys is a Builder task (enable System Fields on a table, or open the object’s settings), not an API call this app can make for you.
Build with Knack
Three routes to the same 5 actions. The Workflow tab is generated from Knack'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.
Create Record
record-create Create a record from field values. Returns the created record, including its id.
Delete Record
record-delete Permanently delete a single record. There is no trash to recover it from.
List Records
record-list List an Object's records, with Knack's own filters, sorting and pagination.
Update Record
record-update Update a record's field values. Fields left out of the payload are unchanged.
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 Knack's real ids.
{
"manifestVersion": "2",
"name": "knack-example",
"steps": [
{
"id": "record-create",
"uses": {
"app": "io.w6w.knack",
"action": "record-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"objectKey": "<objectKey>",
"fields": "<fields>"
}
}
]
}Here are some of the things you can do
-
Create Record
performrecord-create -
Get Record
readrecord-get -
List Records
searchrecord-list -
Update Record
performrecord-update
+1 more action 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 Knack, 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 Knack. 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: "record-create",
payload: {
objectKey: "<value>",
fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action record-create --payload '{"objectKey":"<value>","fields":"<value>"}'Give an AI agent Knack — without giving it Knack'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.knack#record-create",
"input": {
"objectKey": "<objectKey>",
"fields": "<fields>"
}
}
}
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 Knack 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
Knack'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. Knack itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Knack declares its own checks, so its health is a property of the app rather than something the host guesses at.
Knack platform status
Component status from status.knack.com. Covers the API, Builder, Live App and Flows, plus Knack's own marketing site and support tooling.
API plan & rate limit headroom
Reads X-PlanLimit-* (daily plan cap) and X-RateLimit-* (10 requests/second on every plan) response headers from a minimal record read, per docs.knack.com/reference/api-limits.