Three importable n8n workflows that turn one piece of content into a week of distribution: AI digests from any RSS feed, one-click rewrites for X, LinkedIn and email, and a publish queue that reminds you exactly when to post.
Schedule Trigger fetches any RSS feed every 6 hours, summarizes each new item into two sentences plus a headline with AI, filters out empty results, and emails you one clean digest. Point it at your niche feeds and never read a raw feed again.
POST /convert with a long text and a platform (x, linkedin, email). The workflow rewrites it per platform — X gets ≤280 characters with hashtags, LinkedIn gets a hook plus four short paragraphs with a CTA, email gets a subject line and body — and sends the result straight to your inbox.
POST /queue with your content and it starts a cadence: immediate confirmation, then publish reminders at 6 hours, 24 hours, and 72 hours. Your distribution schedule runs itself; you just paste the text when the reminder lands.
| Requirement | Details |
|---|---|
| n8n | v1.60+ self-hosted (Docker) or n8n Cloud |
| LLM key | OpenAI-compatible API key for summaries and rewrites |
| SMTP credentials in n8n (Gmail SMTP or any provider) |
w1-rss-digest.jsonw2-content-converter.jsonw3-publish-queue.jsonsetup-guide.pdf — import steps, env config, curl tests, customization, FAQEverything ships as one ZIP. Valid n8n v1 import format, core nodes only, no exotic dependencies.
Card payment via Stripe. After payment you come back to this page and download the ZIP below.
Buy the pack for $49 →Payments processed by Stripe. No card data touches this site.
After the payment completes, download the package:
Download content-repurposing-pack.zip ↓Questions about the files? Write to [email protected] — we answer within one business day.
Any valid RSS 2.0 or Atom feed. The guide shows how to swap the URL by editing one field in the config node.
Yes — every interval (6h fetch, 6/18/48h queue waits) is a single number in a Wait or Schedule node.
The pack writes and queues content and reminds you to post. Direct posting needs platform APIs with their own credentials; the guide explains how to swap the email step for a native API call if you have keys.
No. One payment, files are yours forever.