Planning tomorrow's clinic
Sarah Chen, practice manager at Northwind Physio, asked who was booked tomorrow. Memtro listed each appointment by calendar with its start time, type and client name.
Who is booked tomorrow, and when is the next free slot?
Acuity Scheduling, also known as Squarespace Scheduling, connects Memtro to your bookings. It reads appointments in a date range with start time, type, calendar and client, appointment types with durations and listed prices, staff and location calendars, and open slots by day or month. Intake forms and notes are never read. When asked, and once an administrator has granted the action by name, it books, reschedules, updates and cancels appointments, blocks off calendar time, and adds or updates clients. Cancelling is permanent. Clients are emailed and texted about a booking, move or cancellation only when you ask for that.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Acuity Scheduling tool, reads what it needs, and answers with the source cited.
These tools change something in Acuity Scheduling. 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 Acuity Scheduling for you. Each event can start a job, with the event as its input. Acuity Scheduling signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Acuity Scheduling 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 tomorrow?
When is the next free slot for an initial assessment?
Which days next month have free time on Sarah's calendar?
What appointments does priya@acme.co.uk have coming up?
Move Tom Baker's Thursday follow-up to Friday at 10 and let him know.
Sarah Chen, practice manager at Northwind Physio, asked who was booked tomorrow. Memtro listed each appointment by calendar with its start time, type and client name.
Tom Reilly, on reception at Northwind Physio, asked Memtro to move James Patel's Thursday assessment to the first free slot on Friday and tell him. Memtro checked Friday's availability, rescheduled the appointment, and Acuity emailed and texted James the new time.
The teams that lean on Acuity Scheduling most, a question each of them asks, and what they connect beside it.
A record in Acuity Scheduling 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 Acuity, go to Integrations → API and click View credentials.
Copy the User ID shown above the API key, then copy the API key. The key has no scopes and can change everything in the account, so Memtro changes something only for actions an administrator has granted.
In Memtro, open Connections → Acuity Scheduling and paste them into User ID and API key.
Ask "Who is booked tomorrow?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Acuity Scheduling tools are the same everywhere.
Only when you ask, and only what it has been granted: book an Acuity appointment for a client; reschedule an Acuity appointment; update an Acuity appointment's client details, labels or form answers; cancel an Acuity appointment; block off time on an Acuity calendar; add a client to Acuity; update an Acuity client's details. 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.
User ID and API key. In Acuity, go to Integrations → API and click View credentials.
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 Acuity Scheduling 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