Research, write, QA — then publish Tuesday, Wednesday, Thursday at 8:30am.
A 20-node n8n engine. Six RSS feeds. Three sequential Claude Sonnet 4.6 calls — analysis, post, editor. Nothing goes live under a QA score of 75. Buyer-facing posts, not builder tutorials.
Everyone knows they should post. Almost nobody does it three times a week.
LinkedIn compounds for B2B services — if the cadence holds. The friction is research, a voice that does not sound like a tool, and actually pressing publish. This workflow removes those steps. The human job left on the published build is glancing at the Sheets log.
Configured for an AI-automation niche and a personal profile (Azam Ali on the live write-up). Feeds, brand-voice node, and hashtags are meant to be swapped — not a locked “Hyxil-only” publisher.
Most business owners think they are losing leads because of bad ads. They are not. They are losing them in the follow-up gap. A new client came to me with 80 enquiries a month and no system to track them. Half were replied to days late. Some not at all. We built one automation. Now every lead gets a response in under 2 minutes, 24/7. What in your business only happens because someone remembers to do it?
B2B operators who need presence without a content team
Marketing agencies, SaaS, consultants, coaches, recruiters — anyone whose next client can come from a feed. Change the Config node (niche, voice, RSS, hashtags, QA floor, recency window, schedule). You do not rebuild the eight stages.
Founders who disappear for two weeks
Cron is 8:30am Tue/Wed/Thu whether or not anyone is at the desk. That is the point of the schedule.
Agencies white-labelling a voice
One Config edit per client. Same analyse → write → QA → LinkedIn API path.
LinkedIn Engine — n8n canvas
The live 20-node run: six RSS feeds, three Claude passes (analyse, write, QA 75+), then auto-publish Tuesday / Wednesday / Thursday at 8:30am.
Eight stages. Three Claude calls. Zero “write me a post” one-shots.
Cron — 30 8 * * 2,3,4
8:30am Tuesday, Wednesday, Thursday. No button. The workflow runs even if the profile owner is offline.
Six RSS feeds, last three days
Published sources: n8n Blog, Zapier Blog, Reddit r/n8n, r/AI_Agents (top of day), r/automation (top of day), plus a Google News search scoped to AI automation and agents.
Score, then pick one unused URL
Freshness starts at 120 and drops one point per hour of age. +6 per keyword hit (ai, report, study, data, launch, 2026, research, guide, case study, google). Already-logged URLs are excluded. Thin titles and snippets lose.
Fetch and clean the article
HTML in, scripts/nav/cookies stripped, up to 7,000 characters of readable text. Under 250 characters falls back to the RSS snippet.
Claude call 1 — six-section analysis
Not a summary. Core thesis, 3–5 insights in Claude’s words, hard numbers only if present (never invented), so-what for a practitioner, one expert angle, and a business-owner translation (money, time, missed leads — no tech language).
Claude call 2 — the post
120–220 words from the analysis, not the raw article. Scroll-stopping hook. Tools named at most once. “I build / my clients / we set up.” Fail condition in the prompt: if it could teach another builder how to do the work, rewrite until a buyer thinks they need this person to build it.
Claude call 3 — QA, min 75
Score 0–100. Grammar, originality, invented-fact check, AI-sounding language, hook, audience fit. Fixable issues get an improvedPost. Unsalvageable drafts are blocked. Only 75+ publishes.
LinkedIn API + Sheets log
Public post on the personal profile. Then date, source title/URL, QA score, and post text are appended so that URL cannot win again.
A single “read this and write a post” prompt is generic
Analyse first
Call 1 forces perspective before any line of the post exists.
Write from the brief
Call 2 drafts from the six sections, not a paste of the article.
Edit, don’t just flag
Call 3 rewrites when it can. The floor is 75, not “looks fine.”
Buyer, not builder
The fail rule is the difference between inbound and a tutorial nobody hires from.
The other seven in this portfolio
LinkedIn Engine — short answers
Will it publish a weak draft?
Can it post on weekends or every weekday?
Is this only for automation consultants?
Does it invent statistics?
How is this different from the WhatsApp agent?
Want a three-day publishing engine on your profile?
We will walk the 20-node canvas — feeds, scoring, three Claude passes, QA 75, LinkedIn API — and retune the Config node to your voice.