Tracing a price change
Dan Fletcher, head of marketing at Acme Ltd, spotted a new price on the pricing page. Memtro read the space's activity log and showed that Sarah Chen had published the story on Tuesday afternoon.
What changed on our Storyblok pages this week, and who changed it?
Storyblok connects Memtro to one space in your headless CMS. It reads stories with their published state, unpublished changes, tags and last author, opens a story's draft text, and reads the activity log, discussions, assets and datasources. When asked and once an administrator has granted the action by name, it can create, update, duplicate, publish, schedule or unpublish stories, start, reply to and resolve discussions, and change datasource entries. Publishing puts a page live on your public site. Deleting a story, an asset or a datasource entry is permanent. The token expires on its set date.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Storyblok tool, reads what it needs, and answers with the source cited.
These tools change something in Storyblok. 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 Storyblok for you. Each event can start a job, with the event as its input. Storyblok signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Storyblok 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 changed on the pricing page this week?
Which blog stories have unpublished changes?
Which discussions on the homepage are still unsolved?
Which images have no alt text?
Schedule the spring launch story to publish at 9am on Monday.
Dan Fletcher, head of marketing at Acme Ltd, spotted a new price on the pricing page. Memtro read the space's activity log and showed that Sarah Chen had published the story on Tuesday afternoon.
Maya Okafor, content lead at BigCo, asked Memtro to put the launch announcement live at 9am on Friday and to tell the editors on its open discussion. Memtro scheduled the story to publish then and replied in the discussion, whose participants Storyblok may notify. The page went live on the site at nine without anyone acting.
The teams that lean on Storyblok most, a question each of them asks, and what they connect beside it.
A record in Storyblok 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 Storyblok, go to My account → Account settings → Personal access tokens and choose Generate New Token.
Choose Only selected spaces, pick this space, give read access to Spaces, Stories, Assets and Datasources, and write access only where you will grant actions. Copy the token, which is shown once.
In Memtro, open Connections → Storyblok and enter Personal access token, Space ID and, if the space is not in the EU, Region.
Ask: what changed on the pricing page this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Storyblok tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Storyblok story or folder (a draft unless publish is set); update a Storyblok story (optionally publishing it); publish a Storyblok story (live on the site); unpublish a Storyblok story (taken off the site); delete a Storyblok story (permanent); duplicate a Storyblok story into a folder; schedule a Storyblok story to publish; start a discussion on a Storyblok story field; reply to a Storyblok discussion; resolve a Storyblok discussion; add a Storyblok datasource entry; change a Storyblok datasource entry; delete a Storyblok datasource entry; delete a Storyblok asset (pages using it lose the file). 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.
Personal access token and Space ID. In Storyblok, go to My account → Account settings → Personal access tokens and choose Generate New Token.
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 Storyblok 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