Build workflows with Claude

Claude can draft a complete n8n workflow from a plain description of your process. The draft is rarely perfect, but it gets you to a working version much faster than starting from an empty canvas. This article gives you a repeatable method: describe, draft, review, test, publish.

Two ways to work

Route	How it works	Best for
Through the n8n MCP server	Claude looks up the nodes on your instance, writes the workflow, validates it and saves it in n8n	Regular building, bigger workflows
Workflow JSON	Claude writes the workflow as JSON, you paste or import it	A quick one-off, or when MCP is not set up

The MCP route is more reliable, because Claude checks node names and settings against your actual n8n version. Set it up first with Use the n8n MCP server. If you use Claude Code, the official n8n Skills add n8n best practices on top.

Step 1: Prepare credentials

Create the credentials the workflow will need in n8n first, for example your Gmail and Slack accounts. See Connect your apps with credentials. When Claude creates a workflow over MCP, n8n assigns matching credentials it finds. Claude never sees the secrets themselves.

Step 2: Describe the process

Brief Claude like a new colleague. Cover:

1. Trigger: what starts it (a new email, a form, every Monday at 9:00).
2. Input: what the data looks like, ideally with one real example.
3. Steps: what should happen, in order, including decisions.
4. Output: where the result goes and what it looks like.
5. Edge cases: what to do when data is missing or something fails.

For more on briefing, see Brief Claude like a colleague.

Step 3: Let Claude draft it

Example prompts:

Build an n8n workflow that runs every weekday at 8:30 Amsterdam time.
It reads yesterday's new rows from the Google Sheet "Leads 2026",
skips rows without an email address, and posts a short summary
to the Slack channel #sales: number of new leads and the top 3 by budget.
Use my existing Google Sheets and Slack credentials. Do not publish yet.

Create a workflow with an n8n Form Trigger for event registrations
(name, email, company, dietary needs). Store each registration in a
data table called "Event registrations" and stop duplicates by email.
Add a sticky note that explains each step in plain language.

Open the workflow "Invoice intake" and add error handling:
retry the Google Drive upload 3 times, and set my "Error alerts"
workflow as its error workflow. Show me what you changed.

Without MCP, end your prompt with: “Return the workflow as n8n workflow JSON that I can paste into the canvas.” Then copy the JSON, click an empty spot on the n8n canvas and paste (Ctrl+V or Cmd+V). Or save it as a .json file and use Import from File in the workflow menu.

Tip: Ask Claude to explain its plan before it builds. Correcting a plan costs one message. Correcting a finished workflow costs many.

Step 4: Review every node

Open the workflow in n8n and go through it from left to right:

1. Check each node does what you asked, with the right operation and fields.
2. Check every node that talks to an app has the right credential selected. HTTP Request nodes usually need you to pick the credential yourself.
3. Check expressions point to real fields. The expression preview shows the actual value, or an error when a field does not exist.
4. Check the trigger settings: schedule times, timezone, mailbox, form fields.
5. Look for anything Claude assumed. Ask it to list its assumptions if unsure.

Warning: Pasted JSON can contain node versions or settings that do not match your n8n version. If a node shows a warning, ask Claude to fix it, or rebuild that node by hand.

Step 5: Test with pinned data

Never test a new workflow against live customers.

1. Run the trigger once with realistic test data, or paste sample data into its output.
2. Pin the trigger output so every test reuses it.
3. Select Execute workflow and inspect each node’s output.
4. Replace actions with side effects (sending emails, updating a CRM) with a test address or a test record while you iterate.

Over MCP, you can also ask: “Test this workflow with realistic pinned data and tell me which nodes fail.” Claude can generate sample data for the trigger and for nodes that call outside services, then run the logic in between.

Step 6: Publish and watch

1. Click Publish, or ask Claude to publish it.
2. Watch the Executions tab for the first real runs.
3. Add an error workflow so failures reach you. See Error handling and alerts.

When you need changes later, ask Claude to update the existing workflow rather than build a new one. n8n keeps a version history, so you can always restore an earlier version.

Next steps

• Use the n8n MCP server
• Turn a business process into an agentic workflow
• Error handling and alerts
• Brief Claude like a colleague