Planning the week
Priya Sharma, operations manager at Acme Ltd, asked who was off next week. Memtro listed each day's absences with leave type and half days, and noted the bank holiday on Monday.
Who is off next week, and which leave requests are waiting for approval?
Timetastic connects Memtro to your staff leave. It reads who is off on which days, with leave bookings, public holidays and non-working days, and leave requests with their type, dates, duration and status. It also reads users with their department and approver, departments, leave types and public holidays. When asked, and once an administrator has granted the action by name, it can book leave for a person, approve, decline or cancel a request, add time off in lieu, add a department, and add or archive a user. The reason given for leave is never shown.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Timetastic tool, reads what it needs, and answers with the source cited.
These tools change something in Timetastic. 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 Timetastic 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 off next week?
Which leave requests are waiting for approval?
Who in the support team is off on Friday?
Which public holidays are coming up in the UK this year?
Approve Maya's leave request for the 14th and let her know
Priya Sharma, operations manager at Acme Ltd, asked who was off next week. Memtro listed each day's absences with leave type and half days, and noted the bank holiday on Monday.
Dan Fletcher, engineering manager at Northwind, asked Memtro to approve Tom Reilly's pending leave request for the end of the month and tell him. Memtro approved it in Timetastic, which emailed Tom as usual. The other requests stayed pending.
The teams that lean on Timetastic most, a question each of them asks, and what they connect beside it.
A record in Timetastic 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.
Sign in to Timetastic as an administrator and open app.timetastic.co.uk/api.
Copy the API token shown. It carries the administrator's permissions over the whole organisation's leave, and renewing it replaces the old one.
In Memtro, open Connections → Timetastic and paste it into API token.
Ask your first question: who is off next week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Timetastic tools are the same everywhere.
Only when you ask, and only what it has been granted: book leave for one person, optionally e-mailing them and their approver; approve a pending leave request, optionally e-mailing the person; decline a pending leave request, optionally e-mailing the person (cannot be undone); cancel a leave booking (cannot be undone); add time off in lieu (TOIL) to a person's allowance for a year; add a department with its manager; add a user, optionally sending them a welcome e-mail to sign in; archive a user, logging them out of Timetastic. 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. Sign in to Timetastic as an administrator and open app.timetastic.co.uk/api.
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