Open requests
Sarah Chen, operations manager at Acme Ltd, asked which equipment requests were still open. Memtro searched the requests table for rows with status open, sorted by date, and listed them with their requester and item.
Which rows in our Budibase requests table are still open, and who can use the app?
Budibase shows you the tables, columns and rows of one workspace, with filtered searches and sorting. Memtro also reads its views and saved queries, the tenant's workspaces, and users by id and global role only. When asked and granted, it can add, change or delete rows, and run a saved query, which may write to the system behind it. It can publish or unpublish a workspace, delete a table or view, and add, change or remove users and their roles. The API key acts as its user, with that user's roles, so a dedicated user is safer.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Budibase tool, reads what it needs, and answers with the source cited.
These tools change something in Budibase. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Budibase is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which rows in the requests table are still open?
What columns does the assets table have?
Which saved queries does this workspace have?
Which users have admin access?
Mark request 1042 as approved.
Sarah Chen, operations manager at Acme Ltd, asked which equipment requests were still open. Memtro searched the requests table for rows with status open, sorted by date, and listed them with their requester and item.
Dan Fletcher, facilities lead at Northwind, asked Memtro to mark one request as approved. With the action granted, Memtro read the row first, then changed its status column, which can start the app's row automations.
The teams that lean on Budibase most, a question each of them asks, and what they connect beside it.
A record in Budibase is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Budibase portal, open your user menu → View API key and generate a key. Generating a new key invalidates the old one.
Open Connections → Budibase in Memtro and paste the API key and the Workspace id from the builder address. Set Budibase host only if you self-host.
An administrator grants actions such as delete a row or publish a workspace by name to the teams that may use them. A Workspace id starting app_dev_ works on development data.
Ask which rows in the requests table are still open.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Budibase tools are the same everywhere.
Only when you ask, and only what it has been granted: add a row to a table; change column values on a row; delete a row (permanent); run one of the workspace's saved queries (it may write to the database or API behind it); publish a workspace, making its current version live; unpublish a workspace, taking it offline for its users; delete a table and all of its rows (permanent); delete a view (permanent); add a user to the Budibase tenant; change a user's name or global builder, admin and app roles; delete a user (permanent); give named users a role, builder or admin access, or take it away. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and workspace id. In the Budibase portal, open your user menu → View API key and generate a key. Generating a new key invalidates the old one.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time