Ask who still has to sign a contract in Documenso, and send a reminder.
Connect Documenso with an API token and Memtro reads one team's documents and templates with each recipient's signing status, an envelope's audit trail, folders and attachments. Leave the host blank for Documenso Cloud or name your self-hosted server. Signing links are never read. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create documents from templates and send them, which emails every signer at once, resend signing emails, place fields, manage recipients and attachments, cancel or permanently delete documents, and manage folders.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Documenso tool, reads what it needs, and answers with the source cited.
These tools change something in Documenso. 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 Documenso, choosing the same kinds; the tab shows Documenso's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Documenso sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Documenso 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.
Documenso + MemtroHas the Northwind contract been signed yet?
Who still has to sign the Brightwave Ltd NDA?
When did Dan Fletcher open the Acme order form?
Which documents were rejected or cancelled last month?
Send a reminder to everyone who has not signed the BigCo renewal
The account lead asks who has not signed the Northwind renewal. Memtro reads the document: Priya Nair signed on Monday, the finance director opened it on Tuesday but has not signed. With the action granted, Memtro resends his signing email.
Dan Fletcher asks Memtro to send the standard order form to Laura Bennett at Acme. Memtro creates the document from the order form template with Laura as signer and sends it, so Documenso emails her a signing link at once.
The teams that lean on Documenso most, a question each of them asks, and what they connect beside it.
A record in Documenso 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 Documenso open Team → Team Settings → API Tokens → Create Token, name it Memtro and pick an expiry. The token sees one team's documents with full API access and no scopes
Leave Host blank for Documenso Cloud (app.documenso.com), or type your self-hosted server's host name only, a public DNS name with a publicly trusted certificate, on a release with the v2 envelope API
Paste the API token, which starts api_ and is shown once, into Connections → Documenso in Memtro and connect
Ask what is still waiting for signature
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Documenso tools are the same everywhere.
Only when you ask, and only what it has been granted: make a draft document signable without emailing anyone (links are shared from Documenso); resend the signing email to recipients who have not acted; add recipients to a document (a pending document may invite them at once); change a recipient's name, email, role or signing order; remove a recipient from a document; rename a document, change its external id or move it to a folder; duplicate a document or template; cancel a pending document (its signing links stop working); delete a document permanently; create a folder; rename, move or pin a folder; delete a folder; create a document from a template, as a draft or sent to its signers; place signature and other fields on a draft document; remove a field from a document; record that a recipient declined to sign; attach a link to a document; change an attachment's label or link; remove an attachment; remove one file from a document. 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. In Documenso open Team → Team Settings → API Tokens → Create Token, name it Memtro and pick an expiry. The token sees one team's documents with full API access and no scopes.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Documenso, choosing the same kinds; the tab shows Documenso'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
