Morning failure check
The operations lead asks what broke overnight. Memtro reads the execution history, finds six errors across two workflows, and gives each run's start time and duration, without any of the records that passed through.
Ask which n8n workflows failed today, and what each workflow is built from.
Connect n8n with your host and an API key and Memtro reads workflows with whether they are active, their node types and tags, and execution history with status, mode, start, stop and duration. Node parameters, credentials, variables and the data that passed through are never read. When you ask, and once an administrator has granted them by name, it can publish or unpublish a workflow, which turns its triggers on or off, archive or tag workflows, retry a failed execution, which repeats whatever it does outside n8n, and stop executions. Deleting a workflow or execution is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right n8n tool, reads what it needs, and answers with the source cited.
These tools change something in n8n. 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.
Once n8n 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 workflows failed today?
Is the invoice sync workflow active, and when did it last run?
Which workflows use the Slack node?
Retry last night's failed CRM import
Unpublish the old Acme lead routing workflow
The operations lead asks what broke overnight. Memtro reads the execution history, finds six errors across two workflows, and gives each run's start time and duration, without any of the records that passed through.
The CRM was down at 02:00 and the Northwind import failed. Once it is back, Priya Nair asks Memtro to retry the run. With the action granted, Memtro starts a new execution, which repeats the import and uses an execution on the plan, and reports that it succeeded.
The teams that lean on n8n most, a question each of them asks, and what they connect beside it.
A record in n8n 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.
The n8n API is not available during the n8n Cloud free trial
In n8n open Settings → n8n API → Create an API key, as a dedicated n8n user with access only to the projects Memtro should see. Outside Enterprise the key has all of that user's rights with no scopes. Label it Memtro, choose an expiry and copy it
In Connections → n8n in Memtro type the Host only: <name>.app.n8n.cloud, or your self-hosted server's public DNS name with a publicly trusted certificate, no https:// or path. Paste the API key
Ask which workflows failed today
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The n8n tools are the same everywhere.
Only when you ask, and only what it has been granted: create a tag (refused if the name already exists); delete a tag (workflows that carried it lose the label); publish a workflow so its triggers go live; unpublish a workflow so its triggers stop; archive a workflow, or restore an archived one; delete a workflow (permanent); set a workflow's tags (replaces its list); retry a failed execution (repeats what the workflow does); stop a running or waiting execution; stop one workflow's queued, running or waiting executions; delete an execution record (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.
Host and API key. The n8n API is not available during the n8n Cloud free trial.
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