Weekend cover check
Dan Fletcher, general manager at Acme Hotels, asked who was on shift in the restaurant this weekend. Memtro listed each shift with its times, employee group and employee, and named two shifts with nobody assigned.
Who is working this weekend, and which shifts are still open?
Planday holds your staff rota, and Memtro reads it so managers get quick answers about who is working. It reads shifts by date, department, employee, group and status, and employees by name with their departments and groups. It also reads departments, employee groups, positions, shift types and absence requests. When asked and granted, it can create, assign, approve, publish and delete shifts, and approve or deny absence. It can also punch employees in or out, and create, invite, deactivate or reactivate them. Contact details, pay and absence balances are never returned. Only an Administrator can open API Access.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Planday tool, reads what it needs, and answers with the source cited.
These tools change something in Planday. 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 Planday 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 working in the kitchen this Saturday?
Which shifts next week are still open?
Which absence requests are waiting for a decision?
Which employees are in the bar staff group?
Approve Maya Okafor's absence request for next Friday.
Dan Fletcher, general manager at Acme Hotels, asked who was on shift in the restaurant this weekend. Memtro listed each shift with its times, employee group and employee, and named two shifts with nobody assigned.
Sarah Chen, front-of-house supervisor at Northwind, asked Memtro to give Saturday's open bar shift to Tom Reilly. Memtro assigned it, and Tom saw the shift in his Planday schedule.
The teams that lean on Planday most, a question each of them asks, and what they connect beside it.
A record in Planday 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 Planday, an Administrator opens Settings, then Integrations, then API Access, creates an app with the read and action scopes needed and authorises it. Scopes cannot be added later.
In Memtro, open Connections → Planday and paste the App ID and the Refresh token from the Token column. Connect each portal separately.
An administrator grants the shift, absence, punch clock and employee actions by name only to the managers who may use them.
Ask who is working this weekend.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Planday tools are the same everywhere.
Only when you ask, and only what it has been granted: create a shift; assign a shift to an employee, or make it open; approve a shift for payroll; publish draft shifts so employees see them; delete a shift; approve an absence request; deny an absence request; punch an employee in; punch an employee out; create an employee; send an employee their Planday invitation; deactivate an employee; reactivate an employee. 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.
App ID and Refresh token. In Planday, an Administrator opens Settings, then Integrations, then API Access, creates an app with the read and action scopes needed and authorises it. Scopes cannot be added later.
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