Ask whether a contract has been signed, and who in Yousign is still to sign it.
Connect Yousign with an API key and Memtro reads signature requests with each signer's status and when they signed, along with saved contacts and templates. Signing links are never returned. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can draft requests, add signers, send a request out for signing, which emails signers outside the company and cannot be recalled, send reminders, pause, resume, cancel or reactivate requests, and manage contacts. Cancelling a request is permanent, and some deletions can never be retrieved.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Yousign tool, reads what it needs, and answers with the source cited.
These tools change something in Yousign. 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 Yousign for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Yousign signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Yousign 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.
Has the Northwind renewal contract been signed yet?
Which signature requests are still waiting on someone, and on whom?
Who signed the Brightwave Ltd NDA, and when?
Which requests expired or were declined last month?
Remind the Northwind finance director to sign the renewal
Before the kick-off call the account lead asks whether the Northwind contract is signed. Memtro finds the request and lists its three signers with their status: Dan Fletcher signed on Tuesday, and the finance director has been notified but has not signed.
Priya Sharma asks Memtro to chase the Northwind finance director, who has had the renewal for a week. Memtro checks the request is still out for signing and that she has not signed, then has Yousign email her a reminder, which cannot be unsent.
The teams that lean on Yousign most, a question each of them asks, and what they connect beside it.
A record in Yousign 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 Yousign open API → API keys, create a key, give it a description and choose its scope: the whole organisation or one workspace
Production access needs a paid Yousign API plan. The free API trial gives sandbox keys only, and sandbox and production keys are separate
In Memtro open Connections → Yousign, paste the API key, set Environment to production or sandbox to match the key, and connect
Ask what is still waiting for signature this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Yousign tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft signature request (stays a draft, with email delivery off, until somebody sends it in Yousign); create a contact; send a Yousign signature request for signing (activate it); cancel a Yousign signature request; remind a signer to sign; remind an approver to approve; add a signer to a Yousign signature request; remove a signer from a Yousign signature request; change a Yousign signature request's name, delivery, order, expiry or decline setting; delete a Yousign signature request; pause a Yousign signature request; resume a paused Yousign signature request; reactivate an expired Yousign signature request with a new expiry; change a Yousign contact; delete a Yousign contact. 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 Yousign open API → API keys, create a key, give it a description and choose its scope: the whole organisation or one workspace.
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 Yousign 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
