Which Tookan deliveries failed today, and which agents are free right now?
Tookan connects Memtro to your delivery and field-service dispatch. It reads tasks by date, status, agent, team or order id, with timings, agent and team, plus task counts by status and deleted tasks. It reads agents with availability and tags, and teams. When asked and granted, it can create, reschedule, assign, cancel or delete tasks, force a status, mark a task ready to dispatch, message agents, block or unblock agents, and manage customers. Tookan can tell Memtro as a task's status changes, and a job can start on it. Customer contact details, addresses and agent locations are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tookan tool, reads what it needs, and answers with the source cited.
These tools change something in Tookan. 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, then add the address it shows as a webhook in Tookan, choosing the same kinds; the tab shows Tookan's own steps. Each event can start a job, with the event as its input. Tookan sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Tookan 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.
Tookan + MemtroWhich deliveries failed today?
Which agents in the North team are free right now?
How many tasks are unassigned this week?
When was order 5521 delivered, and by which agent?
Reschedule the pickup for order 5530 to 3pm tomorrow.
Dan Fletcher, dispatch manager at Northwind, asked which deliveries failed yesterday and who carried them. Memtro listed the failed delivery tasks with order id, agent and team, and when each was started and completed. He spoke to those agents before the morning briefing.
Acme Ltd set a job to start when a Tookan task became Failed. When one arrived, Memtro read the task by its job id and listed the free agents in the same team. Priya Sharma, dispatch lead, saw the summary in Memtro and reassigned the delivery to one of them.
The teams that lean on Tookan most, a question each of them asks, and what they connect beside it.
A record in Tookan 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 Tookan, open Menu, then Settings, then API Keys, and copy the v2 API key. It has full access to the account, as Tookan has no read-only key.
In Memtro, open Connections → Tookan and paste the API key.
An administrator grants the dispatch actions by name to the teams that may use them, since several notify agents or customers.
Ask which deliveries failed today. Events are turned on from the connection's Events tab, and the address is then added in Tookan's notification settings.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tookan tools are the same everywhere.
Only when you ask, and only what it has been granted: create a pickup, delivery or appointment task (can notify the customer and agents); reschedule tasks to a new start and end time; assign a task to an agent in a team (notifies the agent); auto-assign a task within its team; force a task's status, such as successful or failed (can notify the customer); cancel a task; delete a task; mark a task ready to dispatch (pushes to its agent); send a push message to agents; block or unblock agents; add a customer; edit a customer; delete 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.
API key. In Tookan, open Menu, then Settings, then API Keys, and copy the v2 API key. It has full access to the account, as Tookan has no read-only key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tookan, choosing the same kinds; the tab shows Tookan's own steps. 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
