← Catalog

Content factory for micro-agencies: competitor monitoring, rewriting, and auto-publishing on n8n
8 importable JSON files for n8n (Workflow → Import from File). Documentation and setup instructions — in text form (markdown), included with the product.

Content factory for micro-agencies: competitor monitoring, rewriting, and auto-publishing on n8n

Version 1.0.0 Updated: 2026-09-13 Quality: 78/100

8 ready-made n8n workflows: they monitor competitors, rewrite fresh content, check uniqueness, adapt Tone of Voice, and publish on behalf of the client.

📁 What is inside (ZIP, 9 files)
  • 01_competitor_monitor.json
  • 02_content_rewriter.json
  • 03_plagiarism_checker.json
  • 04_tov_adapter.json
  • 05_auto_publisher.json
  • 06_content_pipeline_orchestrator.json
  • 07_competitor_alert.json
  • 08_content_calendar_sync.json
  • README.md

Problem

Micro-agencies spend 10–20 hours a week manually monitoring competitors, copying and rewriting content, checking uniqueness, and publishing. ChatGPT doesn't do this: it doesn't track websites in real time, doesn't compare against what's already been collected, doesn't check uniqueness, and doesn't publish to the client's channels.

Solution

The n8n workflow suite automates the entire cycle. The monitor (01) collects only new materials and writes to Telegram/Slack. The rewriter (02) rewrites via an LLM, the checker (03) calculates uniqueness and finds matches, the adapter (04) tailors the text to the Tone of Voice, and the publisher (05) posts to WordPress, Telegram, VK, and LinkedIn and logs the result. The orchestrator (06) runs all of this daily on its own, the alert (07) instantly reacts to an important competitor publication, and the calendar sync (08) keeps deadlines from being missed.

More details

This is a set of eight importable n8n workflows that cover the full cycle of working with competitors' content: from detecting a new publication to releasing finished material on the client's channel. The workflows communicate with each other through a shared database (Google Sheets / Airtable) and Webhook calls, but each can also be launched and used separately. Workflow 01 "Competitor Monitor" runs on a schedule every 6 hours, takes a list of competitor URLs from Google Sheets, pulls new articles and posts via RSS, sitemap, or HTML parsing (HTTP Request + HTML Extract), compares hashes with already collected materials, and saves only what's new. It immediately writes about findings to Telegram or Slack. Workflow 02 "Content Rewriter" receives text or a URL via Webhook along with Tone of Voice parameters and, through an LLM (OpenAI/Claude), rewrites the material: the meaning is preserved, while the structure and wording change. The response is returned in JSON. Workflow 03 "Plagiarism Checker" receives text, splits it into shingles, checks it against a local database of published content (Airtable/Google Sheets), and, if necessary, calls a uniqueness-check API, returning the uniqueness percentage and a list of matches. Workflow 04 "ToV Adapter" takes the client's Tone of Voice profile from Google Sheets or from the request and, through an LLM, adjusts the style, vocabulary, and sentence length to match the brand voice. Workflow 05 "Auto Publisher" publishes the finished text with a headline, image, and tags to WordPress, Telegram, VK, and LinkedIn via API, can delay publication using Wait, and logs the result to Google Sheets. Workflow 06 "Content Pipeline Orchestrator" runs daily and automatically executes the full cycle: it pulls new materials from the database, rewrites them, checks uniqueness, adapts ToV, and publishes. All steps are built in as nodes, so the orchestrator works autonomously when the input data is filled in. Workflow 07 "Competitor Alert" immediately checks a specific competitor URL via Webhook, compares the hash, and sends a detailed notification to Telegram or Email with a brief summary and a link. Workflow 08 "Content Calendar Sync" synchronizes scheduled materials from Google Sheets with Google Calendar once a day and sends reminders to the person responsible. As a result, the micro-agency gets not a prompt or an instruction, but a working system: fresh content appears on the client's channels without manual copying, and uniqueness and style risks are addressed at the pipeline stage.

Features

  • Scheduled monitoring of a list of competitor URLs every 6 hours via RSS, sitemap, or HTML parsing (HTTP Request + HTML Extract)
  • Comparison by hashes with previously collected materials in Google Sheets/Airtable — only new content is saved
  • Notifications about new competitor publications in Telegram or Slack
  • Rewriting text or URL via LLM (OpenAI/Claude) while preserving meaning and changing structure and wording
  • Uniqueness check: splitting into shingles, cross-checking against a local database of published content, and calling a uniqueness-check API
  • Adapting text to the client's Tone of Voice (formal, friendly, expert, etc.) via LLM
  • Auto-publishing to WordPress, Telegram, VK, and LinkedIn via API with support for scheduled posting and logging to Google Sheets
  • Daily autonomous full-cycle orchestrator: collection → rewrite → check → adaptation → publication
  • Real-time alert for a specific competitor URL with a brief summary and link in Telegram/Email
  • Syncing the content plan from Google Sheets with Google Calendar and reminders to the responsible person

What you get

  • 01_competitor_monitor.json — scheduled competitor monitoring workflow with notifications
  • 02_content_rewriter.json — text or URL rewriting workflow via LLM through Webhook
  • 03_plagiarism_checker.json — uniqueness checking workflow using shingles and an external API
  • 04_tov_adapter.json — workflow for adapting text to the client's Tone of Voice
  • 05_auto_publisher.json — publishing workflow for WordPress, Telegram, VK, LinkedIn with logging
  • 06_content_pipeline_orchestrator.json — daily orchestrator for the full content cycle
  • 07_competitor_alert.json — instant alert workflow based on a competitor's URL
  • 08_content_calendar_sync.json — workflow for syncing the content plan with Google Calendar

Installation guide

1) Install n8n (self-hosted or Cloud) version 1.x. 2) Import all 8 JSON files via the Workflow → Import from File menu. 3) Create a Google Sheets with tabs: competitors (URL, source type), collected content (URL, hash, text, date), published (text, date, channel), content plan (date, topic, status, owner), ToV profiles (client, style, vocabulary, sentence length). 4) Connect credentials: Google Sheets, Airtable (optional), OpenAI or Claude, Telegram/Slack, WordPress, VK, LinkedIn, Email, uniqueness check API. 5) Fill in the Google Sheets with competitors and client ToV profiles. 6) Activate workflows 01 and 06 on a schedule, the rest — via Webhook. 7) Test it on a test URL and a test publishing channel.

Requirements

n8n version 1.x (self-hosted or Cloud). Accounts and API keys: Google Sheets and Google Calendar, OpenAI or Anthropic Claude, Telegram Bot or Slack Webhook, WordPress (REST API + application password), VK API, LinkedIn API, Email (SMTP or service). Optional: Airtable for the content database, Text.ru API or Content-Watch for external uniqueness checking. Basic understanding of how n8n and Webhook work.

Options and pricing

Choose the level that suits you:

  • Basic — $17 · The main set of product files.
  • Standard — $29 · Full set + implementation guide.
  • Extended — $46 · Everything from Standard + extended materials and updates.

Frequently asked questions

What is included?

8 ready-made n8n workflows: they monitor competitors, rewrite fresh content, check uniqueness, adapt Tone of Voice, and publish on behalf of the client.

In what format will I receive the files?

After payment you get a secure link and a ZIP archive with all materials. The link is shown on the order page and available via the Telegram bot.

How long is the download link valid?

The link is active for 24 hours, up to 5 downloads.

Do I need special skills?

The product is designed for entrepreneurs and specialists. A step-by-step guide is included; no programming skills required.

Can I get a refund?

For refunds, contact support: [email protected].

See also