Connecting Claude to n8n: Build Workflows by Describing Them
The reel showed the idea in 60 seconds. This page goes deeper on how Claude and n8n actually work together, what you can build, and where it still trips up.
Claude can read n8n's node structure and build workflows from a plain description.
The skill shifts from building nodes to describing outcomes clearly.
Start with small jobs like lead scraping or a daily brief before anything complex.
You still need to read what Claude builds, because it guesses when context is thin.
As promised in the reel
Get the workflow, prompts and setup.
The exact thing, ready to use. Copy it, change the parts in [BRACKETS], go.
Workflow
Daily location brief workflow
In the reel: “Want me to show you how to build the daily brief?”
Get an automated daily brief that checks your location and suggests what to do that day.
A daily automation that checks your current location and generates recommendations for what to do that day, like a personal daily brief.
1Connect Claude to n8n via the API so you can describe workflows in natural language.
2Create a new workflow in n8n and add a schedule trigger set to run once every day.
3Add a step that determines your current location (for example from a calendar, a location source, or a manual input).
4Pass your location into a Claude node and prompt it to generate recommendations for what to do that day based on where you are.
5Add a delivery step to send the brief to yourself (for example email or a messaging channel).
6Activate the workflow so it runs automatically each day.
How to use it: Build this in n8n using Claude connected via API. Replace the placeholders with your own details before running.
Rebuilt from what the reel shows. Swap in your own details.
Prompt
Claude prompt to build the daily brief in n8n
In the reel: “Prompt into Claude exactly what kind of workflow you'd like to build.”
Hand Claude a clear description so it builds the daily brief workflow for you.
Build me an n8n workflow that runs once every day and acts as a daily brief. Each day it should check my current location, which is [HOW_YOUR_LOCATION_IS_DETERMINED, e.g. pulled from my calendar / a manual input]. Based on my location, generate a short brief of what I could potentially do that day in that place. Then send the brief to me via [DELIVERY_METHOD, e.g. email / Telegram]. Set it to trigger automatically at [TIME_OF_DAY].
How to use it: Paste into Claude once it is connected to n8n via API. Fill in the bracketed details first.
Rebuilt from what the reel shows. Swap in your own details.
Prompt
Claude prompt to build a Google Maps lead list workflow
In the reel: “Build workflows where you collect leads via Google Maps for local businesses.”
Get a workflow that pulls local business leads so you can reach out to them.
Build me an n8n workflow that collects leads from Google Maps. I'm looking for local businesses in [LOCATION/AREA] that are [DOING X OR Y, e.g. restaurants, dentists, gyms]. For each business, collect [FIELDS YOU WANT, e.g. name, address, phone, website]. Output the results as a lead list in [FORMAT, e.g. a Google Sheet] so I can connect with them.
How to use it: Paste into Claude once it is connected to n8n via API. Fill in the brackets first.
Rebuilt from what the reel shows. Swap in your own details.
Prompt
Claude prompt to build a Meta API scraping workflow
In the reel: “You can build meta API scraping workflows.”
Get a workflow that scrapes data from the Meta API.
Build me an n8n workflow that scrapes data from the Meta API. I want to collect [WHAT DATA YOU WANT, e.g. ad performance, page posts]. Pull it on a [SCHEDULE, e.g. daily] basis and store the results in [DESTINATION, e.g. a Google Sheet].
How to use it: Paste into Claude once it is connected to n8n via API. Fill in the brackets first.
Rebuilt from what the reel shows. Swap in your own details.
Setup
Connect Claude to n8n via API
In the reel: “Connect Claude with n8n via the API.”
Set up the connection so you can describe workflows to Claude and have it build them in n8n.
1Have an n8n instance running and a Claude account with API access.
2Connect Claude to n8n through the API following the official documentation.
3Describe the workflow you want to Claude in plain language.
4Let Claude generate the workflow in n8n instead of building it manually.
5Review the generated workflow in n8n and activate it.
How to use it: Follow in order. Use the official n8n and Claude documentation for the exact credential steps.
Rebuilt from what the reel shows. Swap in your own details.
Going deeper
What actually connects here
Claude and n8n talk through the API, and that connection is what makes the whole thing work.
n8n is a visual automation tool. You normally drag nodes around, wire them together, and configure each one by hand. That is where the two-hour tutorials come from.
When you hook Claude into it, you skip the dragging. You describe the workflow in normal language and Claude assembles the node structure for you. It understands the JSON that defines an n8n workflow, so it can write that structure directly instead of making you click through it.
The three things I've built so far
Meta API scraping was the first. I described what fields I wanted pulled and Claude set up the request flow without me touching the docs.
The second was a lead list from Google Maps. You tell it the business type and the area, and it builds a workflow that collects local businesses you can reach out to. Useful if you sell anything to small local shops.
The third is the one people kept asking about. A daily brief that checks where I am and suggests what to do that day. I built it in Sicily, so every morning it reads my location and gives me a short rundown. Nothing fancy under the hood, just a location check feeding into a prompt.
The skill quietly moved
The hard part used to be knowing n8n. Which node does what, how to chain them, how to format a tricky API call.
Now the hard part is describing what you want. Claude builds fast, but it builds exactly what you say, including the parts you said sloppily.
My read is that clear thinking about the outcome now matters more than tool knowledge. If you can explain the workflow to a smart intern in two sentences, Claude can usually build it. If you can't explain it, the tool won't save you.
Where it still trips up
Claude guesses when it lacks context, and those guesses can look convincing while being wrong.
I keep seeing it assume an API returns data in one shape when it returns another. The workflow looks finished and fails on the first real run. So you still open it, read the nodes, and test with real data before trusting it.
Treat the first build as a draft. Describe, generate, run, correct. That loop is faster than any tutorial, but it is still a loop and not a single button.
A sensible place to start
Pick something small and boring for your first build.
The daily brief is a good one because the logic is simple and you see the result every morning, so you notice fast when it misbehaves. Lead scraping is another, since the output is an obvious list you can eyeball.
Resist the urge to make your first project a ten-step monster. Get one honest working flow, understand why it works, then stack from there. That first win teaches you more than any guide.
Want to go deeper?
Let's look at it together.
One call, one on one. We take this and apply it to your account or your workflow.