In short: I asked Claude to build an n8n workflow that turns one blog post into three LinkedIn drafts and saves them to my Notion content calendar. Claude generated the complete workflow file and setup instructions. I imported the file into n8n, added my API key, connected Notion, and had it running the same evening, with no coding and no manual node building.
I use n8n to automate parts of my marketing work, but I have a confession. I don't code, and I have never enjoyed building workflows by hand. Dragging nodes around a canvas and guessing how they connect is exactly the kind of task that makes automation feel harder than the work it replaces.
So this time I skipped all of that. I described what I wanted to Claude, and it built the entire workflow for me. In this post I'll walk you through exactly what I did, what went wrong along the way, and how you can set up the same thing yourself, even if you have never opened n8n before.
What does this automation do?
The workflow takes one blog post and turns it into three ready-to-edit LinkedIn drafts inside a Notion content calendar. Here's the flow. I paste in a blog post, either the link or the full text, and the workflow does three things:
- It reads the blog post.
- It writes three different LinkedIn posts based on it, each with a different angle. One is practical, one is an opinion or pushback, and one is a short observation or story.
- It saves each post as its own row in my Notion content calendar, marked as Draft, so I know I still need to edit them before publishing.
That last part matters. This is not a publish-and-forget machine. It gives me three solid starting points instead of a blank page, and I still put my own voice on top before anything goes live.
How do you stop AI drafts from sounding like AI?
You give the AI strict, specific writing rules and build them into the automation itself, so every draft follows them without you having to repeat yourself.
If you have ever asked AI to write a LinkedIn post, you know the problem. The drafts come back sounding like AI. The same phrases, the same rhythm, the same fake punchiness. I used to spend so much time rewriting drafts that the automation saved me nothing.
So when I asked Claude to build this workflow, I gave it rules to bake in permanently:
- No em dashes, ever.
- Never open with a rhetorical question.
- Full sentences only, no short punchy fragments for effect.
- A list of banned phrases, including "game-changer", "unlock", "dive into", "leverage", "in today's landscape", "the truth is", and "here's the thing".
- Sound like a person talking, not a brand.
- 120 to 200 words per post, no hashtags, no emoji.
These rules now live inside the workflow. Every draft it produces follows them, and that is the difference between drafts I can actually use and drafts I have to rewrite from scratch.
What do you need before you start?
You need four things, and all of them work on free or trial plans:
- An n8n account. I'm on the free trial of their cloud version, and everything here works on it.
- A Notion account with a database for your content calendar. I'll show you the exact setup below.
- A Claude API key from Anthropic. This is separate from a regular Claude subscription, and I'll explain it in a moment.
- The workflow file itself, which Claude generates for you.
A few quick definitions before we go further, because these words get thrown around a lot:
A JSON file is a text file that describes the whole workflow. n8n reads it and rebuilds everything for you. It does not contain any API keys, you add those yourself.
A node is one step in the workflow. Each box on the n8n screen is a node, and each one does a single job, like fetching the blog post, writing the drafts, or saving to Notion.
An API key is like a password that lets n8n use your Claude account. You create it once, paste it into n8n, and keep it private.
Step 1: Ask Claude to build the workflow
I opened Claude and described the automation in plain language. What I wanted it to do, my writing rules, what each Notion row should contain, and the fact that I'm not technical and needed everything explained like I had never done this before.
Claude came back with a ready-made workflow file and a full setup guide, including what to click and in what order. It also told me in advance what was most likely to go wrong on the first run, which turned out to be very useful.
One tip if you try this yourself. Be specific about the output you want in Notion. I told Claude that each row needed the post title, the full text, the angle, a status set to Draft, and a suggested day to post. Because I spelled that out, the workflow arrived already matching what I needed.
Step 2: Set up the Notion database
The workflow needs somewhere to put the drafts, and the column names have to match exactly what the workflow expects. Mine uses five columns:
- Title, which is the built-in title column renamed
- Post Text, type Text
- Angle, type Select
- Status, type Select, with a Draft option
- Suggested Day, type Select
One important detail on the Status column. Notion has two similar-looking property types, a plain Select and a special Status type with colored groups like To-do and In progress. The workflow needs the plain Select. The special Status type will cause an error.
You can build this table by hand in two minutes, or you can ask Notion AI to create it for you. I did the latter, and it worked well.
After creating the database, there is one step almost everyone forgets, including me at first. You have to connect the database to n8n. Go to notion.so/my-integrations, create an integration, copy the secret it gives you, then go back to your database page in Notion, click the three dots in the top corner, find Connections, and add your integration. Without this step, n8n cannot see your database at all, and it simply will not show up in any list.
Step 3: Get your Claude API key
This part I didn't show in my video, so here it is in full.
The API key comes from the Claude Console at console.anthropic.com, which is separate from the regular Claude app. Even if you pay for a Claude subscription, the API is billed on its own. Sign in, add a small amount of credit under Billing, then go to API Keys and create a key. Five dollars of credit lasts a long time here, since each run of this workflow costs a few cents at most.
Name the key something you'll recognize, like n8n. When you click create, the full key appears once and only once, so copy it immediately and keep it somewhere safe until you paste it into n8n. Treat it like a password. Anyone who has it can spend your credit.
Step 4: Import the workflow into n8n
This is the part that used to be the hard part, and now it takes under a minute.
In n8n, create a new blank workflow, click the three dots in the top right of the editor, and choose Import from File. Select the JSON file Claude gave you. The entire workflow appears on the canvas, every node already connected.
If you see exclamation marks on some nodes, don't worry. An exclamation mark means that step is missing a setting or an account connection. Click the node and it will show you what it needs. In this workflow, only two nodes need anything from you:
- The Anthropic Claude node. Open it, create a new credential, paste in your API key, and pick a model from the dropdown.
- The Notion node. Open it, create a credential with the integration secret from step 2, then choose your Content Calendar from the database dropdown.
That is the entire setup.
Step 5: Run it
Click Execute Workflow at the bottom of the canvas. A simple form opens in a new tab with one text box. Paste in a blog post link or the full text, and submit.
Back in n8n, you can watch the nodes light up green one by one as each step finishes. When the last one turns green, open Notion.
Three drafts, three different angles, all marked as Draft, each with a suggested day to post. From pasting the link to seeing the rows in Notion took under a minute.
What went wrong the first time, and how I fixed it
I want to be honest about this, because the first run failed, and the reason is the single most common mistake with this kind of setup.
I originally pointed the workflow at an existing Notion database I already used for content planning. That database had its own columns, things like Platform, Format, and Publish Date. The workflow arrived carrying fields called Post Text, Angle, Status, and Suggested Day, found no columns with those names, and Notion rejected the whole request with a vague "Bad request" error.
The fix was simple once I understood the problem. The workflow and the database just have to agree on column names, spelled and capitalized exactly the same. I created a fresh database with the right columns, connected it, re-selected it in the Notion node, and the next run worked perfectly.
So if your run fails at the Notion step, check three things. First, that the database is connected to your integration. Second, that every column name matches exactly, including capitalization. Third, that your Status column is a plain Select and not Notion's special Status type.
Is it worth setting up?
For me, absolutely. The setup took one evening, most of which was me learning things I'll never have to learn again. Now, every time I publish a blog post, I get three LinkedIn drafts in my calendar for the cost of pasting a link and waiting a minute.
The drafts are not finished posts, and I don't want them to be. They are starting points that already follow my rules and don't sound like AI, which means my editing pass is about adding my perspective rather than deleting clichés.
If you don't code and n8n has always felt out of reach, this is the way in. You don't have to learn how to build workflows anymore. You just have to get good at describing what you want, and as a marketer, describing things clearly is already your job.
Frequently asked questions
Do I need to know how to code to build this?
No. Claude generates the complete workflow file, and n8n rebuilds it when you import the file. The only manual steps are pasting in your API key, connecting your Notion account, and picking your database from a dropdown.
How much does it cost to run?
A few cents per run. The n8n free trial covers the workflow itself, and the Claude API charges only for what you use. Five dollars of API credit covers dozens of runs.
Can I use a different AI model instead of Claude?
Yes. n8n supports several AI providers, so the same structure works with other models. I use Claude because the writing quality with custom rules is the whole point of this workflow for me, and it's the tool I already build with daily.
Does it publish directly to LinkedIn?
No, and that's deliberate. Every post lands in Notion marked as Draft so I can edit it in my own voice before publishing. Automating the publishing step is possible, but I don't recommend posting AI drafts unedited.
Why did my workflow fail at the Notion step?
Almost always one of three things: the database isn't connected to your Notion integration, a column name doesn't exactly match what the workflow expects, or your Status column uses Notion's special Status type instead of a plain Select.
Is my API key inside the workflow file?
No. The JSON file contains only the workflow structure. Keys are stored separately in n8n's credential system, so you can share the file without exposing anything private.