Summarize n8n executions and data tables
Manus counts runs and errors for each workflow, finds the slowest runs and lists your data tables, then writes it up as a short report.
Build and run n8n workflows by describing them in chat
Connect your own n8n, hosted by n8n or on your own server, and Manus works as your n8n AI agent: it builds workflows from your description, tests and runs them, and checks executions and data tables. It isn’t n8n’s AI Workflow Builder; it connects through the MCP server in your n8n.
First, connect n8n in Manus
An n8n AI workflow builder that works from chat
Describe the trigger, the steps and where results should go. As your n8n workflow builder, Manus writes the nodes, checks them and shows them to you before saving. As an n8n AI agent builder, it can also add a Chat Trigger and an AI Agent node with the tools you name.
Debug n8n workflow automation when an execution fails
Manus reads the execution, points to the node that failed and why, and suggests a fix. Before anything is published, it can save the fix as a draft and test n8n AI workflows with sample data in place of the trigger, app nodes and HTTP requests, so the test doesn’t call your connected apps.
Run a workflow from chat through the n8n MCP server
Name a workflow that has MCP access and give it the input it needs. Manus runs the published version and brings the result back to the conversation, without an n8n ChatGPT integration to set up for it.
n8n AI automation reports and scheduled checks
Pull execution history and data tables into one summary, or have Manus check on your workflows at a set time.
n8n workflow ideas for scheduled tasks
These n8n workflow examples pair well with a Manus scheduled task: a Monday check on failed runs, a daily check that every workflow ran and a monthly list of workflows that haven’t run.
See scheduled tasks and triggersConnect Manus as your n8n MCP client
Most “n8n MCP Claude” or “n8n ChatGPT MCP” guides add n8n’s MCP server to that app. In Manus, n8n is already in Connectors: paste your server URL and access token once.
Turn on MCP in n8n
Open Settings > Instance-level MCP and select Enable MCP access. An instance owner or admin needs to do this.
Choose the workflows
Turn on Available in MCP for each workflow Manus should open, run or change. Workflows Manus builds are turned on for you.
Paste the URL and token in Manus
In n8n, select Connect and open the API key tab to copy the server URL and access token. Then open Connectors in Manus, select n8n and paste them in.
Paste both into Manus Connectors
More n8n integrations and guides
- MCP connectorsConnect your apps to Manus with MCP connectors
- AutomationsPut your connected apps to work on a schedule.
Zapier connectorTake real actions across 8,000+ apps with Zapier MCP- GitHub connectorSelect a repository for a code task.
- MCP connectors guideLearn how to connect and use MCP servers.
- n8n MCP server docsn8n’s guide to turning on MCP access.
Questions about the n8n AI agent and MCP in Manus
How do I connect n8n to Manus?
In n8n, open Settings > Instance-level MCP and select Enable MCP access (an instance owner or admin can do this). Select Connect, open the API key tab and copy the server URL and access token. Then open Connectors in Manus, select n8n and paste them in.
Does Manus support n8n MCP?
Yes. The n8n connector links Manus to the MCP server built into your n8n, with Manus as the MCP client. An n8n ChatGPT connector or a Claude setup adds that same server inside those apps. In Manus, you add it once in Connectors.
Can I connect n8n Cloud and self-hosted n8n?
Yes. Both have Instance-level MCP under Settings, and you use the server URL your own instance shows there. Building and editing workflows through MCP needs n8n 2.13 or later.
Which n8n MCP tools can Manus use?
It uses the tools your n8n version provides, for example: search, build, edit, test, run, publish, unpublish and archive workflows; check executions; find, create and rename data tables, add or delete columns and add rows; and list credential names. Newer n8n versions add more. Manus can only open, run or change workflows that have MCP access turned on.
Will Manus break my existing n8n workflows?
Only workflows with MCP access turned on can be opened, run or changed; others appear in search as previews. Edits stay in draft until the workflow is published, so the live version keeps running, and n8n keeps a version history you can restore. Publishing, unpublishing and data table changes, such as deleting a column, take effect right away and aren’t in that history, so ask Manus to show the planned changes and wait for your OK.
Is Manus the n8n AI Workflow Builder or n8n Assistant?
No. The AI Workflow Builder and n8n Assistant are n8n’s own AI features inside n8n. Manus is a separate AI agent, not an n8n AI assistant built into the editor. It works in your n8n through the MCP server, and the same task can also use your files, the web and your other connected apps.
Can Manus see my n8n credentials?
It can list the names and types of credentials your n8n account can use, so new nodes can be linked to them. n8n doesn’t send the secret values to MCP clients.
Can I start from n8n workflow templates?
Yes. Import the template into your n8n and turn on MCP access for it. Manus can then read it, test it and change it to fit your apps.
Can I use n8n and Zapier together in Manus?
Yes. They are separate connectors, and one task can use both. If you are looking at Zapier AI agents to act across your apps, the Zapier connector page shows what Manus can do there.
Do my workflows keep running when Manus isn’t open?
Yes. Published workflows run in n8n on their own triggers. Manus is only needed to build, test, run or check them from a chat. For regular checks, set up a Manus scheduled task.