Tomorrow's yoga roster
Maya Okafor, studio manager at Northwind Fitness, asked who was booked into tomorrow's 7am yoga. Memtro read the class roster and gave each customer's name and booking status, with the class's capacity and waitlist.
Who is booked into tomorrow's 7am yoga, and which memberships are expiring?
TeamUp shows how your gym or studio's classes and memberships stand. You see customers by name or email with status, classes by date, venue or instructor with capacity and bookings, a class roster, customers' memberships with dates and status, the membership catalogue, instructors and venues. When asked and granted, Memtro can add customers, resend invitations, book or remove bookings, confirm attendance or mark no-shows, give free memberships, cancel memberships and create classes. TeamUp can tell Memtro when a customer books, a class ends or a membership is cancelled, and a job can start on it. Payment details are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right TeamUp tool, reads what it needs, and answers with the source cited.
These tools change something in TeamUp. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with TeamUp for you. Each event can start a job, with the event as its input. TeamUp signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce TeamUp 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.
Who is booked into tomorrow's 7am yoga?
Which classes this week are full?
Which memberships expire this month?
How many active members does the Unlimited membership have?
Book Sarah Chen into Thursday's 6pm spin class.
Maya Okafor, studio manager at Northwind Fitness, asked who was booked into tomorrow's 7am yoga. Memtro read the class roster and gave each customer's name and booking status, with the class's capacity and waitlist.
At Acme Ltd's gym, a job starts when TeamUp reports a customer did not show. Memtro reads the customer and their memberships, and gives Dan Fletcher, the front desk lead, their membership status and expiry before he calls.
The teams that lean on TeamUp most, a question each of them asks, and what they connect beside it.
A record in TeamUp 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 TeamUp Business Dashboard, an Owner or Admin goes to Settings, Integrations, API Integration, creates an application and adds a token with an expiry and only the permissions needed.
In Memtro, open Connections → TeamUp and paste it into M2M token.
An administrator grants the actions by name, such as Book customer or Cancel membership, to the staff who may use them. Events are turned on from the connection's Events tab, which needs a full admin token.
Ask who is booked into tomorrow's 7am yoga.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The TeamUp tools are the same everywhere.
Only when you ask, and only what it has been granted: add a customer, optionally emailing them an invitation; resend a customer's invitation email; book a customer into a class; remove a customer's booking from a class; confirm a customer attended a class; mark a customer as a no-show for a class; give a customer a free membership; cancel a customer's membership; create a class. 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.
M2M token. In the TeamUp Business Dashboard, an Owner or Admin goes to Settings, Integrations, API Integration, creates an application and adds a token with an expiry and only the permissions needed.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with TeamUp for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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