Hours before invoicing
Sarah Chen, operations manager at Acme Ltd, asked how many billable hours went on BigCo last month. Memtro listed the time entries by project and service with the total, and noted two entries not yet marked billable.
How many hours did we book to this customer last week?
Clockodo connects Memtro to your time tracking. It reads time entries by person, customer, project and service, with hours, billable state and descriptions, and what a clock is running on right now. It also reads customers, projects with deadlines and budgets, services, co-workers and absences with their status. When asked, and once an administrator has granted the action by name, it can add, edit or permanently delete a time entry, start or stop the clock, request an absence, and create a customer or project. Wages, target hours and sick notes are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Clockodo tool, reads what it needs, and answers with the source cited.
These tools change something in Clockodo. 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 Clockodo 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.
How many hours did we book to Acme last week?
What is my clock running on right now?
Who is on holiday next week?
Which projects have a deadline this month?
Log two hours yesterday afternoon on the Northwind website project
Sarah Chen, operations manager at Acme Ltd, asked how many billable hours went on BigCo last month. Memtro listed the time entries by project and service with the total, and noted two entries not yet marked billable.
Dan Fletcher, consultant at Northwind, asked Memtro to log the two hours he spent on the BigCo workshop yesterday. Memtro added the entry in Clockodo against BigCo, the workshop project and the consulting service. Nobody was notified.
The teams that lean on Clockodo most, a question each of them asks, and what they connect beside it.
A record in Clockodo 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 Clockodo, open Personal data and copy your API key. It carries your access rights: an admin's key sees the whole company, a co-worker's only what they may see.
Changing that user's Clockodo password replaces the key, so the connection would need the new one.
In Memtro, open Connections → Clockodo and enter the Clockodo login email and the API key.
Ask your first question: how many hours did we book to Acme last week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Clockodo tools are the same everywhere.
Only when you ask, and only what it has been granted: add a time entry for a customer, project and service; change a time entry's times, description, project, service or billable state; delete a time entry (permanent); start the clock (stops any clock already running); stop a running clock; request an absence such as holiday or home office (absence managers may be told); create a customer; create a project for a customer. 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.
Clockodo login email and API key. In Clockodo, open Personal data and copy your API key. It carries your access rights: an admin's key sees the whole company, a co-worker's only what they may see.
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