Checking an onboarding run
Maya Okafor, an account manager at Acme Ltd, asked how far BigCo's onboarding had got. Memtro found the run, said how many tasks were done of the total, and named the open ones with their assignees and due dates.
How is this set up for a client, and how far has their onboarding checklist got?
Hudu connects Memtro to your IT documentation. It reads client companies, knowledge base articles with their text, processes and their runs with tasks completed, and assets such as devices and licences. Password and confidential fields are always left out. When asked, and once an administrator has granted the action by name, it creates and edits articles, companies and assets, archives them, starts process runs, assigns run tasks, builds process templates and relates records. It never writes a password. Deleting an article is permanent, and a public article can be read by anyone with the link.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Hudu tool, reads what it needs, and answers with the source cited.
These tools change something in Hudu. 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 Hudu 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.
How is the firewall set up for Northwind?
How far has the BigCo onboarding run got?
Which tasks on Acme's onboarding checklist are still not done?
Find the article on Northwind's backup schedule.
Start the onboarding process for Globex and assign the first task to Dan Fletcher.
Maya Okafor, an account manager at Acme Ltd, asked how far BigCo's onboarding had got. Memtro found the run, said how many tasks were done of the total, and named the open ones with their assignees and due dates.
Dan Fletcher, a field engineer at Acme Ltd, asked Memtro to start Globex's onboarding checklist and give him the network survey task due Friday. Memtro started a run of Globex's onboarding process, then set that task's assignee and due date, and Hudu notified Dan of the assignment.
The teams that lean on Hudu most, a question each of them asks, and what they connect beside it.
A record in Hudu 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 Hudu, go to Admin → API Keys → New API Key. Some versions put API Keys under Admin, Basic Information.
Leave password access and exports off. Turn destructive actions on only if Memtro may delete articles. Optionally limit the key to particular companies, then copy it while it is shown.
In Memtro, open Connections → Hudu. Enter the Hudu host as a host name only, with no https:// or path, and paste the API key.
Ask "How far has the Northwind onboarding checklist got?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Hudu tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Hudu knowledge base article; edit a Hudu article; archive a Hudu article; delete a Hudu article; create a Hudu company; update a Hudu company; archive a Hudu company; create a Hudu asset (never a password field); update a Hudu asset's name, serial, model, manufacturer or email; archive a Hudu asset; start a run of a Hudu process; set a Hudu run task's assignees, due date or priority; create a Hudu process template; add a task to a Hudu process template; relate two Hudu records. 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.
Hudu host and API key. In Hudu, go to Admin → API Keys → New API Key. Some versions put API Keys under Admin, Basic Information.
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