Morning defect check
Tom Reilly, fleet manager at Northwind, asked which vehicles had unsafe defects still unresolved. Memtro listed them with the driver's comment and any mechanic's notes, and said which already had a work order.
Which vehicles have open unsafe defects, and how far did each drive last week?
Samsara connects Memtro to your fleet operations. It reads vehicles with their assigned driver, drivers by name, trips with times and distance, hours-of-service violation summaries, DVIR defects, maintenance work orders, issues and dispatch routes. Locations are never read. When asked, and once an administrator has granted the action by name, it creates, updates and cancels work orders, resolves defects, opens issues, records and signs off mechanic DVIRs, creates dispatch routes for drivers and deactivates or reactivates drivers. Resolving a defect or DVIR has no reopen, and deleting a work order or route is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Samsara tool, reads what it needs, and answers with the source cited.
These tools change something in Samsara. 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 Samsara for you. Each event can start a job, with the event as its input. Samsara signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Samsara 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.
Which vehicles have open unsafe defects?
How far did Truck 7 drive last week?
Which drivers had hours-of-service violations this week?
Which work orders are still open?
Create a work order to replace the brake light on Van 12.
Tom Reilly, fleet manager at Northwind, asked which vehicles had unsafe defects still unresolved. Memtro listed them with the driver's comment and any mechanic's notes, and said which already had a work order.
Maya Okafor, maintenance coordinator at Northwind, told Memtro the cracked mirror on Van 12 had been replaced. Memtro marked the defect resolved with the mechanic's notes and set the matching work order to Completed. Drivers and the maintenance team saw the defect resolved in Samsara.
The teams that lean on Samsara most, a question each of them asks, and what they connect beside it.
A record in Samsara 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 the Samsara dashboard, go to Settings → API Tokens and add an API token named Memtro.
Give it Read Vehicles, Drivers, Trips, ELD Compliance Settings (US), Defects, Work Orders, Issues, DVIRs and Routes. Add Write Work Orders, Issues, DVIRs, Defects, Routes or Drivers only for the actions Memtro may take.
In Memtro, open Connections → Samsara, paste the API token, and set Region to us, eu or ca to match your Samsara cloud.
Ask "Which vehicles have open unsafe defects?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Samsara tools are the same everywhere.
Only when you ask, and only what it has been granted: create a maintenance work order for a vehicle or asset; update a work order's status, priority, description, notes, due date or assigned mechanic; cancel a work order, or delete one permanently; mark a vehicle defect resolved, with mechanic's notes; open an issue against a vehicle, trailer or equipment, or change an issue's status, priority, assignee or due date; record a mechanic's DVIR for a vehicle or trailer, or sign off and resolve a DVIR; create a dispatch route with stops for a driver or vehicle, change its name, notes, driver or vehicle, or delete it; deactivate a driver, removing their driver app access, or reactivate them. 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 token and optional region. In the Samsara dashboard, go to Settings → API Tokens and add an API token named Memtro.
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 Samsara 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