Explain why an n8n workflow failed
Name a workflow and the agent reads its latest failed run, finds the node that broke and explains the error in plain words.
Letaido's n8n integrations let one AI agent check runs, clean up workflows and report to 64 other apps.
Each one checked step by step. Open one to watch it run.
Name a workflow and the agent reads its latest failed run, finds the node that broke and explains the error in plain words.
Every Monday, the agent lists last week's failed n8n runs by workflow, with the error that stopped each one, in your ops channel.
The agent finds published workflows with no saved runs in 90 days, shows you the list, and archives the ones you confirm.
Every Monday, the agent adds one row per n8n workflow to your sheet: last week's runs, failures and failure rate.
On the first of each month, the agent runs n8n's security audit and posts the risky credentials, nodes and unused workflows to Slack.
After you fix a workflow, the agent lists its failed runs from the past day and retries the ones you confirm.
Ways to watch, run and manage n8n from outside the editor.
| Option | Set up by asking | Explains what it finds | Runs on its own | No code | Reaches other apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | Yes | |
| n8n's own nodes | No | Partly | Yes | Partly | Yes |
| n8n error workflows | No | No | Yes | Partly | Partly |
| n8n MCP server | Yes | Yes | Partly | Yes | Partly |
| n8n API | No | No | Partly | No | Partly |
| Zapier and Make | Partly | Partly | Yes | Partly | Yes |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job in a chat. The agent uses n8n's API to read runs, workflows and data tables, and can archive, retry or tag. It reports to Slack, Sheets and 62 more apps, on a schedule or when you ask. | Looking after the instance: weekly failure reports, cleanups and plain answers on why a run broke. | It manages n8n. It does not add nodes to n8n or replace its editor. Allow all read operations once per app; approve each kind of write once. |
| n8n's own nodes | n8n's 2,300+ integrations, plus the HTTP Request node for any API, inside workflows you build. | Moving data between apps on a trigger. | You build and maintain each workflow in the editor. |
| n8n error workflows | A workflow that starts with the Error Trigger runs when another workflow fails, for example to send a Slack alert. | An alert the moment one workflow fails. | You link it to each workflow, and it runs each time that workflow fails. |
| n8n MCP server | Lets clients such as Claude Desktop search workflows, run the ones you enable for MCP, and build or edit workflows and data tables. | Running or building workflows while you chat with an AI app. | Each workflow must be enabled for MCP. Scheduling depends on the AI app. |
| n8n API | A REST API for workflows, runs, credentials, data tables, users and more, with an API key. | Scripts and CI pipelines that manage n8n. | Needs developers. Not on an n8n Cloud trial. |
| Zapier and Make | Workflows that call an n8n webhook to start a workflow, or read what an n8n workflow sends back. | Starting an n8n workflow from an app n8n doesn't cover. | Another workflow tool to pay for and maintain. |
Connect n8n once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Save it to repeat on a schedule.
A schedule starts the job, or you do by asking.
In n8n, open Settings, then n8n API, create a key with a label and an expiry, and copy it.
Add the key and your instance's HTTPS address, such as your n8n Cloud address.
The API works on paid n8n Cloud plans and every self-hosted edition. An n8n Cloud trial doesn't include it.
Describe the job and Letaido runs it once in the chat. Allow all read operations once per app; approve each kind of write once. Then save it to repeat.
81 actions in 13 groups. Allow all read operations once per app; approve each kind of write once.
No. Letaido manages n8n, it doesn't extend it. Your workflows keep using n8n's own integrations.
It reads workflows, runs, data tables and audits. It can also archive, publish or tag workflows, retry or stop runs, and update data tables. It has 81 n8n actions in all.
Yes. Letaido connects through n8n's API, which works on paid n8n Cloud plans and every self-hosted edition. An n8n Cloud trial doesn't include it.
In n8n, open Settings, then n8n API, and create a key with a label and an expiry. Paste the key and your instance's HTTPS address into Letaido. On Enterprise you can limit what the key may do.
Yes. n8n's built-in MCP server lets clients such as Claude Desktop search workflows, run the ones you enable, and build or edit workflows. Letaido is not an MCP server. It uses n8n's API, runs jobs on a schedule, and reports to Slack, Google Sheets and other apps.
Yes. n8n's MCP server works with clients such as Claude Desktop, and n8n's docs include setup steps for ChatGPT. Letaido is separate: its own agent, connected to n8n with an API key, that can repeat a job on a schedule.
Yes, if the instance has the public API on and is reachable over HTTPS from the internet.
Allow all read operations once per app; approve each kind of write once.
Connect n8n, then ask for a job like "Explain why my n8n workflow failed". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoBrowse and inspect workflows, their nodes, versions, tags, and sharing details.
Create, update, move, archive, restore, or permanently delete workflows and manage their tags.
Activate or deactivate workflow triggers and run workflows via webhook.
List, inspect, stop, retry, annotate, or delete workflow runs.
Store, view, update, move, test, and delete credentials used by workflow nodes.
Create, read, update, and delete n8n data tables, their columns, and their rows.
Create, rename, move, and delete workflow folders and tags to keep the workspace organized.
Invite, view, update roles for, and remove users on the instance.
Start, monitor, cancel, and read results of evaluation test runs against workflow datasets.
Export workflows, folders, or projects as packages and import them into other instances.
List, install, update, and uninstall community node packages from npm.
View production run summaries, failure rates, and run the instance's security audit.
Raw API passthrough, permission discovery, and OpenTelemetry tracing configuration for the instance.