Waiting on one signer
The account lead asks whether the Northwind renewal is signed. Memtro finds the request awaiting signature: Dan Fletcher signed on Monday, the second signer viewed it on Tuesday and was reminded yesterday but has not signed.
Ask whether a contract has been signed in Dropbox Sign, and who has still to sign.
Connect Dropbox Sign (HelloSign) with an API key and Memtro reads signature requests with title, status, dates and each signer's name, status and signing date, searchable by title, signer, sender and creation date, along with your templates. Form answers and signing links are never shown. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can send documents or a template for signature, which emails every signer a link and is legally binding, remind a signer, correct a signer or expiry, and permanently cancel an incomplete request.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Dropbox Sign tool, reads what it needs, and answers with the source cited.
These tools change something in Dropbox Sign. 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 Dropbox Sign 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 Northwind signed the MSA yet?
What is still awaiting signature across the team?
Why did BigCo decline the order form?
Remind the second signer on the Northwind renewal to sign
Send the standard NDA template to Laura Bennett at Globex for signature
The account lead asks whether the Northwind renewal is signed. Memtro finds the request awaiting signature: Dan Fletcher signed on Monday, the second signer viewed it on Tuesday and was reminded yesterday but has not signed.
Priya Sharma asks Memtro to send the standard NDA to Laura Bennett at Globex. Memtro reads the template, matches Laura to its signer role, and sends the request, and Dropbox Sign emails Laura a link to sign a legally binding copy.
The teams that lean on Dropbox Sign most, a question each of them asks, and what they connect beside it.
A record in Dropbox Sign 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 app.hellosign.com open Settings → API and, under API key, reveal or generate a key (an account can hold up to four)
The key acts as your account: it reads your own requests by default, and the team's when you are on a team, and requests it sends go out from you
In Memtro open Connections → Dropbox Sign, paste the API key and connect
Ask what is still awaiting signature
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Dropbox Sign tools are the same everywhere.
Only when you ask, and only what it has been granted: send a signature request from a template to named signers (emails them a signing link); send a signature request for documents at URLs to named signers (emails them a signing link); remind a signer by email to sign an open request; change a signer's name or email address, or a request's expiry; cancel an incomplete signature request (permanent); remove this account's access to a completed signature request (permanent). 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 app.hellosign.com open Settings → API and, under API key, reveal or generate a key (an account can hold up to four).
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