Counting sign-ups
Maya Okafor, events manager at Northwind, asked how many people filled in the event signup this week. Memtro read the form's submissions since Monday and counted 42, with names and their session choices.
Who filled in our Fillout forms this week, and what did they say?
Fillout connects Memtro to every form in your organisation. It lists the forms and the questions each one asks, and reads a form's submissions by date range, words in the answers or unfinished status, with when, who from, quiz score and the answers. An hourly sync keeps new submissions in memory. Address, phone, payment, signature, location and file answers are always left out. When asked and once an administrator has granted the action by name, it can add submissions to a form, which may fire the form's own emails and integrations, and permanently delete a submission.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fillout tool, reads what it needs, and answers with the source cited.
These tools change something in Fillout. 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 Fillout for you. Each event can start a job, with the event as its input. Fillout signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Fillout 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.
How many people filled in the event signup this week?
What did Acme put in the contact form?
What were the quiz scores on the product training form?
Which submissions to the demo request form mention pricing?
Delete the test submission I sent to the event signup this morning.
Maya Okafor, events manager at Northwind, asked how many people filled in the event signup this week. Memtro read the form's submissions since Monday and counted 42, with names and their session choices.
Tom Reilly, sales lead at BigCo, took a demo booking from Priya Sharma at Acme by phone and asked Memtro to add it to the demo request form. Memtro added one submission with her answers. The form's own emails and integrations may run on it as if she had filled it in.
The teams that lean on Fillout most, a question each of them asks, and what they connect beside it.
A record in Fillout 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 Fillout, open your organisation (top left) → Settings → Developer → API key. Only an organisation admin can see it, and the key has no scopes.
Turn the API on if no key is shown, copy the key, and note whether the base URL is eu-api.fillout.com.
In Memtro, open Connections → Fillout, paste API key, and set Region to eu for an EU account.
Ask: how many people filled in the event signup this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fillout tools are the same everywhere.
Only when you ask, and only what it has been granted: add up to 10 submissions to a Fillout form (may fire the form's own emails and integrations); delete one Fillout submission (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. An hourly sync anchors recently changed Fillout records into memory as entities.
API key. In Fillout, open your organisation (top left) → Settings → Developer → API key. Only an organisation admin can see it, and the key has no scopes.
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 Fillout 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