Chasing payment
On Monday the finance lead asks which invoices are overdue. Memtro reads unpaid invoices and lists four, the largest from Northwind at 4,200 euros due three weeks ago, with each customer's email for the reminder.
Ask Dolibarr which invoices are unpaid and what a customer has ordered.
Connect Dolibarr with your host and an API key and Memtro reads third parties and their contacts, invoices, proposals, orders, projects, tasks and agenda events. The key acts as its user with all of their permissions, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can log time, create and change projects, tasks, events, contacts and tickets, draft invoices, proposals and orders, and validate them with definitive numbering. It can record payments in the books and mark invoices paid, and permanently delete third parties, contacts or time lines.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dolibarr tool, reads what it needs, and answers with the source cited.
These tools change something in Dolibarr. 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.
Once Dolibarr 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 invoices are unpaid and past their due date?
What has Northwind ordered this year?
Which proposals for Acme are still waiting to be signed?
Log three hours on the BigCo migration task for today
Record Northwind's payment of invoice FA2611-0042 into the main bank account
On Monday the finance lead asks which invoices are overdue. Memtro reads unpaid invoices and lists four, the largest from Northwind at 4,200 euros due three weeks ago, with each customer's email for the reminder.
Northwind's transfer arrives, and Sarah Collins asks Memtro to record it against their overdue invoice. With the action granted, Memtro records the invoice's whole remaining amount into the named bank account and Dolibarr classifies the invoice paid. Nobody is emailed.
The teams that lean on Dolibarr most, a question each of them asks, and what they connect beside it.
A record in Dolibarr 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.
An administrator enables the API REST module once in Home → Setup → Modules. Each business module must be enabled too, and endpoints are present since Dolibarr 5.0
Open Users & Groups → (a dedicated user with only the rights Memtro should have) → generate an API key. It acts as that user with all of their permissions and no scopes
In Connections → Dolibarr in Memtro type the Host name only, public over https with a trusted certificate, plus Install path and Port if needed, and paste the API key
Ask which invoices are unpaid and overdue
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dolibarr tools are the same everywhere.
Only when you ask, and only what it has been granted: log time spent on a project task, as the connection's own user; create a third party (customer, prospect or supplier) when none of that name exists; overwrite named fields of an existing third party; delete a third party permanently; delete a time-spent line from a task permanently; add an agenda event for a named owner; create a project; create a task in a project; overwrite a time-spent line; create a draft invoice with lines; create a draft commercial proposal with lines; create a draft customer order with lines; validate an invoice, proposal, order or project (definitive numbering); create a contact; overwrite named fields of a contact; delete a contact permanently; record a payment of an invoice's remaining amount into a named bank account; classify an invoice as paid; reopen a paid invoice as unpaid; close a proposal as signed or refused; close an order as delivered; open a ticket; add a message to a ticket; close or abandon a ticket; assign or unassign a ticket; change a project task; change a project; change or reschedule an agenda event. 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.
Host and API key. An administrator enables the API REST module once in Home → Setup → Modules. Each business module must be enabled too, and endpoints are present since Dolibarr 5.0.
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