A pre-release check
Sarah Chen, content manager at BigCo, asked which blog posts had unpublished changes. Memtro listed three records with status updated and when each was last changed, with a preview of what had changed in each.
Which DatoCMS records have unpublished changes, and what changed this week?
DatoCMS connects Memtro to your project's content. It reads the models, then the records of any model, each with its status as draft, updated or published, its dates and a preview of each field. It opens one record in full and reads the media library. An hourly sync keeps changed records in memory. When asked and once an administrator has granted the action by name, it can create, update, duplicate, publish, schedule or unpublish records, and edit media metadata. Publishing puts content live on your site and can start your builds. Deleting a record or a media asset is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right DatoCMS tool, reads what it needs, and answers with the source cited.
These tools change something in DatoCMS. 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 DatoCMS for you. Each event can start a job, with the event as its input. DatoCMS sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce DatoCMS 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.
Which blog posts have unpublished changes?
What changed in the product catalogue this week?
Which images in the media library have no alt text?
Show me the published version of record 81234.
Publish the three blog posts Sarah updated today.
Sarah Chen, content manager at BigCo, asked which blog posts had unpublished changes. Memtro listed three records with status updated and when each was last changed, with a preview of what had changed in each.
Dan Fletcher, product manager at Acme Ltd, asked Memtro to publish the three updated posts before the newsletter went out. Memtro published the named records, which went live on the site and started the project's publish build in DatoCMS.
The teams that lean on DatoCMS most, a question each of them asks, and what they connect beside it.
A record in DatoCMS 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 DatoCMS, go to your project → Project settings → API tokens and create a new API token, not the built-in full-access one.
Turn on Access the Content Management API, give it a role that can read records and the media library, plus only the create, edit, publish or delete permissions for the actions you will grant, and copy the token.
In Memtro, open Connections → DatoCMS and paste it into API token, filling Environment only for a sandbox.
Ask: which blog posts have unpublished changes?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The DatoCMS tools are the same everywhere.
Only when you ask, and only what it has been granted: create a DatoCMS record (as a draft); update a DatoCMS record's fields; publish a DatoCMS record (live on the site); unpublish a DatoCMS record (taken off the site); delete a DatoCMS record (permanent); duplicate a DatoCMS record; schedule a DatoCMS record to publish; schedule a DatoCMS record to unpublish; publish up to 200 named DatoCMS records at once; edit a DatoCMS media asset's metadata; delete a DatoCMS media asset (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 DatoCMS records into memory as entities.
API token. In DatoCMS, go to your project → Project settings → API tokens and create a new API token, not the built-in full-access one.
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 DatoCMS 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