Which Zuper jobs are scheduled today, and which technicians have them?
Zuper connects Memtro to your field service management. It reads jobs by status, category, priority, customer, technician and schedule, and one job with its status history and notes. It reads job categories and their statuses, customers by company and organisation, users and invoices. When asked and granted, it can create a job, add a note, move a job to a status, assign or unassign technicians, reschedule or delete a job, clock in or out of a job, and create a customer. Customer names, contact details and addresses are never returned, and the key sees only what its user can.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Zuper tool, reads what it needs, and answers with the source cited.
These tools change something in Zuper. 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 Zuper 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 jobs are scheduled today, and who has them?
What is the status history of job 1042?
Which invoices are unpaid and past due?
Which high-priority jobs have no technician assigned?
Add a note to job 1042 saying the part arrives Thursday.
Tom Reilly, service manager at Northwind, asked which jobs were scheduled for today and who had them. Memtro listed them with category, priority, time and assigned technicians, and flagged the high-priority ones with nobody assigned. He assigned those before the vans left.
Maya Okafor, coordinator at Acme Ltd, asked Memtro to move a boiler service job to Friday morning after the customer called. With the action granted, Memtro rescheduled it to the new window. The assigned technician saw the new time in Zuper.
The teams that lean on Zuper most, a question each of them asks, and what they connect beside it.
A record in Zuper 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.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn the Zuper web app, open Settings, then Developer Hub, then API Keys, and create a new key. It has the permissions of its user, so tick Read-only if Memtro should only read.
In Memtro, open Connections → Zuper and paste the Company login name you sign in with and the API key.
An administrator grants the job, assignment and customer actions by name to the teams that may use them. Team Leader and Field Executive keys see only their own scope.
Ask which jobs are scheduled today and who has them.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Zuper tools are the same everywhere.
Only when you ask, and only what it has been granted: create a job (work order) for a customer or organisation; add a note to a job; move a job to another status; assign or unassign technicians on a job; reschedule a job; delete a job (restorable for 90 days); clock in or out of a job as the key's user; create a customer. 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.
Company login name and API key. In the Zuper web app, open Settings, then Developer Hub, then API Keys, and create a new key. It has the permissions of its user, so tick Read-only if Memtro should only read.
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