Review queue at a glance
Priya Sharma, content lead at Acme Ltd, asked which articles were still in review. Memtro read the latest variant of every article and listed those in the Review step with their last change. She chased the oldest first.
Which Kontent.ai articles are still in review?
Kontent.ai connects Memtro to your headless CMS, in one environment. It reads content items, each item's language variants with workflow step, schedule and element text, and the latest variants of a content type. It also reads content types, languages, workflows and assets. When asked and granted, it can create or rename items, set text elements of a draft, move a variant through workflow, publish, unpublish or schedule it, and delete variants, items or unused assets. Kontent.ai can also tell Memtro as content is published, changed or deleted, and a job can start on it. Management API keys expire.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kontent.ai tool, reads what it needs, and answers with the source cited.
These tools change something in Kontent.ai. 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 Kontent.ai for you. Each event can start a job, with the event as its input. Kontent.ai signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Kontent.ai 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 articles are still in review?
What is the workflow step and schedule of the pricing page in German?
What elements does the blog post content type have?
Which languages are active in this environment?
Move the launch announcement to the Review step.
Priya Sharma, content lead at Acme Ltd, asked which articles were still in review. Memtro read the latest variant of every article and listed those in the Review step with their last change. She chased the oldest first.
When a product page variant was published at BigCo, Kontent.ai told Memtro and a job started. It read the item with its element text and noted what had gone live for Tom Reilly, the web manager. Nothing in Kontent.ai changed.
The teams that lean on Kontent.ai most, a question each of them asks, and what they connect beside it.
A record in Kontent.ai 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 Kontent.ai, turn on the Management API for the environment, then open Project settings → API keys and create a Management API key. Only project managers can, and keys expire.
In Memtro, open Connections → Kontent.ai and paste the Environment ID and the Management API key.
Read-only permissions cover questions, while publishing, workflow and delete actions need content permissions. An administrator grants the actions by name to the teams that may use them. Events are turned on from the connection's Events tab, and Memtro registers the webhook.
Ask "Which articles are still in review?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kontent.ai tools are the same everywhere.
Only when you ask, and only what it has been granted: create a content item; rename or recode a content item, or move it to another collection; set text elements of a draft language variant; move a language variant to a workflow step; create a new draft version of a published variant; publish a language variant now or at a set time; unpublish and archive a language variant now or at a set time; schedule publishing and unpublishing of a variant; cancel scheduled publishing; cancel scheduled unpublishing; delete a language variant; delete a content item and all its variants; delete an unused asset. 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.
Environment ID and Management API key. In Kontent.ai, turn on the Management API for the environment, then open Project settings → API keys and create a Management API key. Only project managers can, and keys expire.
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 Kontent.ai 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