Budget check mid-project
Priya Sharma, account director at Acme Ltd, asked how many hours had gone into the Northwind rebrand. Memtro read the project's budget hours and its time entries, and gave the total logged against the budget.
How many hours did we log on each project this week?
Paymo holds your projects, tasks and time, and Memtro reads it for you. It reads projects with clients and budgets, tasks with due dates and priority, and time entries with hours. It also reads timers, comments, clients, people, invoices and expenses. When asked and granted, it can manage tasks, log or edit time, start or stop a timer and comment. It can also create projects, add clients, create draft invoices, void an invoice and add expenses. Paymo can tell Memtro when time is logged, and a job can start on it. Pay rates and contact details are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Paymo tool, reads what it needs, and answers with the source cited.
These tools change something in Paymo. 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 Paymo for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Paymo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Paymo 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 log on each project this week?
Which tasks are overdue on the website redesign?
Who has a timer running right now?
Which invoices are overdue, and for how much?
Log two hours on the Northwind discovery task for today.
Priya Sharma, account director at Acme Ltd, asked how many hours had gone into the Northwind rebrand. Memtro read the project's budget hours and its time entries, and gave the total logged against the budget.
Dan Fletcher, studio manager at BigCo, asked Memtro to draft an invoice for the client's March work. Memtro created a draft invoice in Paymo, which stayed unsent until he reviewed and sent it himself.
The teams that lean on Paymo most, a question each of them asks, and what they connect beside it.
A record in Paymo 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 Paymo, go to My Account, then API Keys, and generate a new API key. It acts as you, with your access.
In Memtro, open Connections → Paymo and paste it into API key.
An administrator grants the task, time, project and invoice actions by name to the teams that may use them. Events are turned on from the connection's Events tab.
Ask how many hours were logged on each project this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Paymo tools are the same everywhere.
Only when you ask, and only what it has been granted: create a task on a project or task list; change, reassign, reprioritise or complete a task; delete a task and the time logged on it; log time on a task; edit a time entry; delete a time entry; start a timer on a task; stop a running timer; comment on a task; create a project; update or archive a project; add a client; create a draft invoice for a client; void an invoice; add an expense for a client. 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 key. In Paymo, go to My Account, then API Keys, and generate a new API key. It acts as you, with your access.
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 Paymo 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