Preparing for the week
Priya Sharma, head of partnerships at Acme Ltd, asked who was booked on her SavvyCal next week. Memtro listed each meeting with time, attendees and the link they booked through, and flagged one awaiting approval.
Who is booked on my calendar through SavvyCal, and through which link?
SavvyCal connects Memtro to your scheduling. It reads meetings whose start falls in a date window, with title, state, organiser and attendees by name and email, and the link each was booked through, with reschedules and cancellations. It also reads your scheduling links with their state, durations and team. When asked, and once an administrator has granted the action by name, it can book a meeting for a guest, who is likely to be emailed an invitation, cancel a meeting for good, and create, change, copy, switch off or permanently delete scheduling links. The token acts as you.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right SavvyCal tool, reads what it needs, and answers with the source cited.
These tools change something in SavvyCal. 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 SavvyCal for you. Each event can start a job, with the event as its input. SavvyCal signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce SavvyCal 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 on my SavvyCal next week?
Which meetings are awaiting approval?
How many meetings were cancelled or rescheduled this month?
What durations does my intro call link offer?
Switch off my intro call link until I am back
Priya Sharma, head of partnerships at Acme Ltd, asked who was booked on her SavvyCal next week. Memtro listed each meeting with time, attendees and the link they booked through, and flagged one awaiting approval.
Dan Fletcher, consultant at BigCo, was going on leave and asked Memtro to stop his intro call link taking bookings. Memtro switched the link off in SavvyCal and reported its new state as disabled. Existing meetings stayed booked and nobody was notified.
The teams that lean on SavvyCal most, a question each of them asks, and what they connect beside it.
A record in SavvyCal 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 SavvyCal, open Settings → Developers → Personal access tokens.
Create a token named Memtro and copy the private key, which starts pt_secret_. It acts as you, so Memtro sees and changes only what you can.
In Memtro, open Connections → SavvyCal and paste it into Personal access token.
Ask your first question: who is booked on my SavvyCal next week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The SavvyCal tools are the same everywhere.
Only when you ask, and only what it has been granted: book a meeting on a scheduling link for a guest (the guest is likely to be emailed an invitation); cancel a booked meeting (attendees are likely to be told); create a personal or team scheduling link; rename a scheduling link or change its slug, description or type; duplicate a scheduling link; disable or re-enable a scheduling link; delete a scheduling link (its booking page stops working). 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.
Personal access token. In SavvyCal, open Settings → Developers → Personal access tokens.
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 SavvyCal 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