Skip to content

Latest commit

 

History

21 Commits

Folders and files

Repository files navigation

Animated NexusNow RSS to Gemini to Blogger pipeline

NexusNow AI News Automation

A living editorial loop for the next tech story.

Use the reference scenario Read NexusNow


Make.com Google Gemini Blogger Every eight hours MIT license



Watch the signal. Extract the facts. Write with Gemini. Publish with guardrails.

What this is: a production-minded Make.com playbook that watches Google News RSS, uses four Gemini editorial stages, filters unsafe or weak outputs, and creates a Blogger post for NexusNow every eight hours.

⚡ Launch in one glance
Input Google News RSS + curated feeds Fresh tech, AI, and gaming signals
Brain 4 × Google Gemini modules Classify → research → write → quality-check
Control Router + skip/log branch Reject duplicates, stale stories, malformed output, and rate-limit cases
Output Blogger → Create a post Draft-first rollout, then automatic publishing

The shortest safe path: copy the public scenario → reconnect your own apps → paste the prompts → test one bundle → keep Blogger in draft mode → switch on the 8-hour schedule.

✨ The loop

flowchart LR
    A[🛰️ Google News / RSS] --> B[🧭 Classify + choose angle]
    B --> C[🔎 Source-backed fact sheet]
    C --> D[✍️ Original Blogger-safe draft]
    D --> E[🛡️ SEO + quality gate]
    E --> F{Router}
    F -->|pass| G[📰 Blogger post]
    F -->|reject / stale / duplicate / rate-limited| H[🧾 Skip + log]
    H --> I[Next scheduled run]
Loading

What makes this more than “RSS in, AI out”

01 · Signal

RSS is only the discovery layer. Every bundle keeps its canonical URL, source, timestamp, and GUID.

02 · Evidence

Gemini separates confirmed facts from unknowns before it writes a single paragraph.

03 · Craft

The writer produces readable, source-linked HTML instead of copied publisher text or Markdown sludge.

04 · Control

A quality gate and explicit skip branch protect the blog from duplicates, hallucinations, and quota storms.

🚀 Build your own in 8 moves

01
Copy
Open the public Make scenario and choose Use the scenario.
02
Connect
Reconnect RSS, Google Gemini, and Blogger with your own accounts.
03
Schedule
Set the scenario to At regular intervals → 8 hours.
04
Prompt
Paste the four prompts from prompts/ into the Gemini modules.
05
Guard
Add freshness, duplicate, JSON-parse, quality-status, and error-handler filters.
06
Draft
Map title, HTML body, and labels to Blogger; keep Is draft = true.
07
Prove
Run one bundle and inspect every module plus the generated Blogger draft.
08
Release
Review at least 20 articles, then promote the Blogger route from draft to publish.

→ Open the full build guide

🧠 The four Gemini stages

Stage Question it answers Guardrail Prompt
Classify Is this a relevant, fresh story with a real reader angle? Skip thin, stale, promotional, or missing-URL items 01-classify-and-angle.md
Fact sheet What is actually supported by the source? Separate confirmed facts from unknowns; no invented quotes or numbers 02-fact-sheet.md
Article draft Can a reader understand what happened and why it matters? Original Blogger-safe HTML, attribution, no prompt leakage 03-article-draft.md
Quality + SEO Is this safe to route to Blogger? Fail closed when a required check is false 04-quality-and-seo.md
🔍 Show the publish gate

The publish route should require all of these conditions:

  • classification decision is publish;
  • quality status is pass;
  • source URL and attribution are present;
  • article body is non-empty and valid HTML;
  • word count is inside the configured range;
  • canonical URL / GUID is not already in the dedupe store;
  • article is inside the freshness window;
  • no prompt text, invented quotes, unsupported claims, or internal metadata is visible.

Anything else goes to the skip/log route with a reason, source URL, run ID, and timestamp.

🗺️ Navigate the repo

Read this When you need it
docs/MAKE-COM-SETUP.md Build or copy the scenario from zero
docs/CONFIGURATION-CHECKLIST.md Confirm accounts, filters, mappings, and rollout settings
docs/CONTENT-SYSTEM.md Define the NexusNow voice and originality policy
docs/OPERATIONS.md Handle retries, quotas, duplicates, bad drafts, and rollback
docs/SCENARIO-REFERENCE.md See what was inferred from the public scenario and screenshot
config/source-catalog.yml Start with public feed examples
scenario/FIELD-MAPPING.md Map Make bundles to Gemini and Blogger fields
scripts/validate-config.ps1 Run a lightweight local repo check

🎛️ Operator dashboard

Cadence
every 08 hours
Destination
NexusNow on Blogger
Mode
draft → review → publish
Owner
ManasSoni-2009

The three rules that keep it healthy

  1. Never publish blind. Keep Blogger in draft mode until a sample set passes review.
  2. Never retry blindly. Retry transient timeouts, 429s, and temporary 5xx errors with backoff; skip malformed or policy-failing bundles.
  3. Never lose the source. Every post and every log record should preserve the original URL and publish timestamp.

RSS is a discovery mechanism, not a license to reproduce a publisher’s article. Summarize in original language, attribute the source, and respect feed terms and applicable law.

📸 Reference scenario

Reference Make.com scenario showing RSS, Gemini, Router, and Blogger modules

The public reference scenario currently shows RSS intake, four Gemini response modules, a Router, a rate-limit skip branch, and Blogger’s Create a post action. Connections and credentials are intentionally not stored here.

🔐 Security note

The public Make scenario is safe to share because private connections are not included. You still need to create your own connections, protect your Gemini/Blogger credentials, and keep tokens out of Git. See the Make scenario-sharing guide before sharing your own automation.

📜 License

MIT — use the playbook, adapt the prompts, and make it yours. See LICENSE.


Built for curious readers, careful automation, and the next useful story.

Releases

Packages

Contributors

Languages