Weekly hours review
Sarah Chen, delivery manager at Acme Ltd, asked how many hours went on the website project last week. Memtro returned tracked, manual and billable hours per person, with the project total.
How many hours did each person track on a Hubstaff project last week?
Hubstaff connects Memtro to your time tracking. It reads tracked, manual and billable hours per person, project and day with totals, and timesheets with their approval state. It also reads members, projects with budgets, clients, tasks, and time-off and manual time requests. When asked and granted, it can log time, manage tasks, projects and clients, request time off, decide time off, manual time and timesheets, and invite people. With events on, Hubstaff tells Memtro when tracking starts or a shift is missed, and a job can start on it. Pay rates, activity levels, screenshots and locations are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Hubstaff tool, reads what it needs, and answers with the source cited.
These tools change something in Hubstaff. 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 Hubstaff for you. Each event can start a job, with the event as its input. Hubstaff signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Hubstaff 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 each person track on the website project last week?
Which timesheets are submitted and waiting for approval?
Which time-off requests start next month?
Which manual time requests are in the review queue?
Create a task on the website project for Maya to update the pricing page.
Sarah Chen, delivery manager at Acme Ltd, asked how many hours went on the website project last week. Memtro returned tracked, manual and billable hours per person, with the project total.
At Northwind, a job starts when Hubstaff reports a shift was missed. It reads the member's time-off requests for that day and tells Dan Fletcher, the team lead, whether approved time off covers it.
The teams that lean on Hubstaff most, a question each of them asks, and what they connect beside it.
A record in Hubstaff 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 Hubstaff, an owner, manager or Manage-IT member opens Settings, Organization, API tokens, creates a token and assigns it to a member. Copy the hsoat_ secret, shown once.
In Memtro, open Connections → Hubstaff and paste the Organization access token. Add the Organization ID only if the member belongs to more than one.
An administrator grants the actions by name, such as approving timesheets, to the teams that may use them. Events are turned on from the connection's Events tab.
Ask how many hours each person tracked on a project last week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Hubstaff tools are the same everywhere.
Only when you ask, and only what it has been granted: log time for a member on a project; create a task on a project; update, reassign or complete a task; delete a task; create a project; update or archive a project; create a client; request time off for a member; approve or deny a time-off request; approve or deny a manual time request; set a timesheet's status (submit, approve, deny or reopen); invite a person to the organization. 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.
Organization access token. In Hubstaff, an owner, manager or Manage-IT member opens Settings, Organization, API tokens, creates a token and assigns it to a member. Copy the hsoat_ secret, shown once.
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 Hubstaff 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