What does Dr Ruiz have tomorrow, and when is the next free physio slot?
Semble connects Memtro to your clinic's diary. It reads appointments by date or by when they changed, practitioners with their specialties, free availability slots, and the practice with its locations and rooms. It never reads a patient's record, notes or details. When asked, and once an administrator has granted them by name, it can book, move or cancel appointments for a patient by id, text or email a patient, and create, change or delete internal staff tasks. Texts and emails reach the patient at once, cannot be recalled, and a text may use SMS credit.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Semble tool, reads what it needs, and answers with the source cited.
These tools change something in Semble. 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 Semble for you. Each event can start a job, with the event as its input. Semble signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Semble 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.
Semble + MemtroWhat does Dr Ruiz have tomorrow?
When is the next free physio slot?
Which appointments changed since yesterday?
Move Thursday's 10am with Dr Ruiz to 2pm the same day.
Create a task for the practice manager to check Thursday's room bookings.
Priya Sharma, practice manager at Northwind, asked what Dr Ruiz has tomorrow and when the next physio slot is free. Memtro listed the appointments with type, location and status, with no patient named, and found the first free slot in local time.
Tom Reilly, clinic lead at Acme Ltd, gave Memtro a patient's Semble id and asked to book them the next free physio slot and send a confirmation. Memtro found Thursday at 11am, booked it with the physiotherapist and turned on Semble's confirmation message, which reached the patient.
The teams that lean on Semble most, a question each of them asks, and what they connect beside it.
A record in Semble 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
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn Semble, open Settings → API credentials and generate a token for Memtro.
Grant bookings, users, availabilitySlots and practice. Add createTask, updateTask, deleteTask, createBooking, updateBooking, deleteBooking, sendSms or sendEmail only for the actions Memtro may take. Grant no patient query, then copy the token.
In Memtro, open Connections → Semble, paste the API token, and set Environment to sandbox only for a sandbox token.
Ask: what does Dr Ruiz have tomorrow?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Semble tools are the same everywhere.
Only when you ask, and only what it has been granted: create an internal task assigned to a member of staff, with no patient attached; change, reassign or close an internal staff task; delete an internal staff task; book an appointment for a patient by id with a practitioner, room and appointment type; move or change an appointment: time, practitioner, room, type, status or comments; cancel an appointment, optionally telling the patient and emailing the practice; send an SMS to a patient by id; send an email to a patient by 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.
API token and optional environment. In Semble, open Settings → API credentials and generate a token for Memtro.
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 Semble 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