Ask what people answered on a Tally form, completed or partial, for any week.
Connect Tally with an API key and Memtro reads the account's forms with status, whether closed, submission counts and dates, a form's questions with response counts, and its submissions with every answer, filtered by completed or partial and by date. 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, publish, rename, close or reopen forms, delete a form to the trash, permanently delete a submission, create workspaces and folders, invite people by email, and remove a user from the organisation.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tally tool, reads what it needs, and answers with the source cited.
These tools change something in Tally. 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 Tally, choosing the same kinds; the tab shows Tally's own steps. Each event can start a job, with the event as its input. Tally signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Tally 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.
What did people say in the customer feedback form this week?
How many partial submissions has the onboarding survey had since Monday?
Which of our Tally forms are closed?
Close the workshop RSVP form with a message that places are full
Draft a form called Workshop RSVP with a name question and an email question, then publish it
The product lead at Brightwave Ltd asks what customers said in the feedback form this week. Memtro reads the completed submissions since Monday, each answer set against its question, and pulls out the three requests that came up more than once.
Priya Nair asks Memtro for an RSVP form for the Northwind workshop. Memtro drafts it with name and email questions and, once she has checked it, publishes it so anyone with the link can answer. When the 40 places fill, Memtro closes the form with a message saying so, keeping every submission.
The teams that lean on Tally most, a question each of them asks, and what they connect beside it.
A record in Tally 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.
Jotform
DataForSEO
Moz API
Hygraph
Paperform
Kajabi
Kontent.ai
Teachable
WufooIn Tally → Settings → API keys choose Create API key and copy it now: Tally shows it once
The key has every permission of the person who created it, since Tally keys have no scopes. Memtro reads with it, and publishes, edits, deletes or invites only when asked and once an administrator has granted that action
In Memtro open Connections → Tally, paste the API key and connect
Ask what people answered on the feedback form this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tally tools are the same everywhere.
Only when you ask, and only what it has been granted: create a new draft form with a title and simple text or email questions, unpublished until someone publishes it; publish a form so anyone with its link can fill it in; rename a form; close a form to new submissions with a message, or reopen it; delete a form to the trash; delete one submission, permanently; create a workspace; create a folder in a workspace, or rename one; invite people by email to workspaces; remove a user from the organisation. 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 Tally → Settings → API keys choose Create API key and copy it now: Tally shows it once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tally, choosing the same kinds; the tab shows Tally'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
