Ask what came in through a Jotform form this week, with every answer.
Connect Jotform with an API key and Memtro reads the account's forms with title, status, submission and unread counts, and the submissions made to one form or across the account, every answer set against its question. 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 clone forms, edit or flag submissions, create, rename and file labels, and delete submissions, forms or labels. Deleting a submission or form is permanent and a deleted form's link stops working. It never submits to a form.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Jotform tool, reads what it needs, and answers with the source cited.
These tools change something in Jotform. 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 Jotform 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.
Jotform + MemtroWhat came in through the event registration form this week?
How many unread submissions does the contact form have?
Show me the latest submissions across all our forms
Which of our forms have had no submissions at all?
Flag the submission from Dan Fletcher on the workshop form
On Friday the events lead asks what came in through the Northwind workshop form this week. Memtro finds the form, reads the submissions created since Monday and lists each person's answers against the questions, with the count of sign-ups still unread.
The office manager at Acme, Priya Sharma, has forty forms and asks Memtro to file the old ones away. Memtro creates a label called Archive and files the forms she names under it, changing nothing in the forms themselves.
The teams that lean on Jotform most, a question each of them asks, and what they connect beside it.
A record in Jotform 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.
DataForSEO
Moz API
Hygraph
Paperform
Kajabi
Kontent.ai
Teachable
WufooIn jotform.com → My Account → API choose Create New Key, set it to Read Access, or Full Access to let Memtro make the changes you allow, and copy it
Jotform caps API calls per key per day by plan, 1,000 on the free Starter plan, resetting at midnight US Eastern
In Memtro open Connections → Jotform, paste the API key, set Region to standard, EU (an account on eu.jotform.com) or HIPAA, and connect
Ask what came in through a form this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Jotform tools are the same everywhere.
Only when you ask, and only what it has been granted: create a label to organise forms in the account, optionally inside another label; clone a form; edit a submission's answers, or mark it read, unread or flagged; delete a submission permanently; rename or recolour a label; file forms under a label; delete a form permanently, with its submissions; delete a label and its sublabels (the forms in it stay). 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 jotform.com → My Account → API choose Create New Key, set it to Read Access, or Full Access to let Memtro make the changes you allow, and copy it.
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
