Pipeline report on demand
Tom Reilly, sales operations manager at BigCo, asked for this week's pipeline. Memtro ran the saved pipeline report in Quickbase and returned its rows as the report defines them.
What is in our Quickbase tables, and what does this saved report show?
Quickbase shows you an app's tables and each table's fields. It queries records with Quickbase's query language, with sorting and paging, and runs saved reports as they are configured. When asked and granted, it can add records to a table, update records by Record ID, and delete records by Record ID. Adding or changing records may fire the table's notifications and automations, as it would for a person. The token acts with its owner's permissions in each app it is assigned to. A dedicated service user with only the roles Memtro needs is the safer owner.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Quickbase tool, reads what it needs, and answers with the source cited.
These tools change something in Quickbase. 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 Quickbase 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 tables are in our operations app?
What fields does the Projects table have?
Which open projects are due this month?
Run the Overdue Invoices report.
Set record 412 in Projects to Done.
Tom Reilly, sales operations manager at BigCo, asked for this week's pipeline. Memtro ran the saved pipeline report in Quickbase and returned its rows as the report defines them.
Maya Okafor, field manager at Northwind, asked Memtro to add yesterday's site visit to the Visits table. With the action granted, Memtro added the record and returned its new Record ID, so her team saw it in the table.
The teams that lean on Quickbase most, a question each of them asks, and what they connect beside it.
A record in Quickbase 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 Quickbase click your name on the global bar, then Profile, then Manage user tokens. Create a new user token and assign it to every app Memtro should reach.
In Memtro open Connections → Quickbase and fill in Realm, User token and App ID, the id after /db/ in the app's address.
An administrator grants the add, update and delete actions by name to the teams that may use them.
Ask: which tables are in our operations app?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Quickbase tools are the same everywhere.
Only when you ask, and only what it has been granted: add records to a table; update records by Record ID; delete records by Record ID. 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.
Realm, user token and app ID. In Quickbase click your name on the global bar, then Profile, then Manage user tokens. Create a new user token and assign it to every app Memtro should reach.
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