Planning around leave
Sarah Chen, engineering manager at Northwind, asked who on her team was off in the next fortnight. Memtro listed the approved time off with dates and days for each person.
Who is off next week, and which expenses and timesheets need approving?
Remote shows you employees and contractors with job title, department, country and status. It reads time off, expenses, timesheets with hours, and payroll runs with their payout dates. When asked and granted, it can approve, decline or cancel time off, answer cancellation requests and record approved leave. It can also approve or send back timesheets, approve, decline or add expenses, add a bonus, and invite a new hire. Remote can tell Memtro as it happens when time off is requested or an expense is submitted, and a job can start on it. Health and family leave show only as leave.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Remote tool, reads what it needs, and answers with the source cited.
These tools change something in Remote. 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 Remote for you. Each event can start a job, with the event as its input. Remote signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Remote 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 expenses are pending approval?
Which timesheets have been submitted but not approved?
When does the next payroll run in Germany pay out?
Which new hires are still onboarding?
Sarah Chen, engineering manager at Northwind, asked who on her team was off in the next fortnight. Memtro listed the approved time off with dates and days for each person.
When a time off request arrived from Remote, a job started for Tom Reilly, people lead at Acme Ltd. It read the approved time off for those dates and told him who else would be away.
The teams that lean on Remote most, a question each of them asks, and what they connect beside it.
A record in Remote 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 Remote open Company Settings, then Integrations & APIs, then Remote API, and generate a token. Choose Read only, Full access, or the endpoints you need. Only a company admin or owner can do this.
In Memtro open Connections → Remote and paste the Customer API token. Memtro picks production or sandbox from its prefix.
An administrator grants the time off, expense and incentive actions by name to the teams that may use them. Events are turned on from the connection's Events tab.
Ask: 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 Remote tools are the same everywhere.
Only when you ask, and only what it has been granted: approve a time off request; decline a time off request (the employee sees the reason); cancel approved time off; approve a time off cancellation request; decline a time off cancellation request; record approved time off for an employee; approve a timesheet (feeds payroll); send a timesheet back to the employee with a reason; approve a pending expense (it is reimbursed through payroll); decline a pending expense with a reason; add an expense for an employee, already approved for reimbursement; add a bonus, commission or allowance for an employee, paid in a coming payroll; delete an incentive that has not started processing; invite a new hire to start self-enrollment. 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.
Customer API token. In Remote open Company Settings, then Integrations & APIs, then Remote API, and generate a token. Choose Read only, Full access, or the endpoints you need. Only a company admin or owner can do this.
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 Remote 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