← Back to library

Only show research findings whose quotes check out

u/Fit-Appointment700 on r/n8n, an n8n node author, shared three workflows built on one rule: the model suggests, and code decides what gets shown. In each, the model must supply exact quotations, and a small script confirms each one is really on the cited page.

  • OutcomeBuild research automations where the model must quote its source and a code step drops any finding whose quote isn't actually on that page.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/Fit-Appointment700 on r/n8n
View original
Works with
n8nMakeZapier

Published Oct 20, 2026Updated Oct 20, 2026AI dry run on sample input: passed Oct 20, 2026Source verified Oct 24, 2026

When should you use it?

  • Research reports or articles go to clients or the public and a made-up citation would be costly
  • You want to refresh old figures in published content without trusting the model's memory

Not for: Quick personal questions where a human reads the sources anyway

What do you need, and what do you get?

You need

  • An automation tool with a code step (the poster used self-hosted n8n)
  • A web search step and a page fetcher
  • A model that returns structured output (JSON)

You get

  • Findings, each with an exact quote and source link that passed the check
  • A list of dropped claims, so you see what failed
  • A plain 'not enough verified material' message when too little survives

How does it work, step by step?

  1. Ask for quotes, not summariesHave the model return each finding as JSON with the exact sentence and the URL it came from, using our prompt.
  2. Check in codeFetch the page and test whether the quoted sentence is really there, after normalizing spaces and quote marks. Drop anything that fails.
  3. Set a floorIf fewer than a set number of findings survive, report that instead of writing anyway.
  4. Write from survivors onlyOnly then ask the model to write the summary, using the verified quotes as its sole material.

The prompt

Our own prompt, inspired by u/Fit-Appointment700 on r/n8n and written to work in n8n, Make and Zapier. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Question: {question}
Read these sources: {sources}
Return JSON only: a list of findings, each with "claim" (your words, one sentence), "quote" (the exact sentence from the source, copied character for character), and "url" (the page it came from).
Rules: only quote text that is on that page; never merge sentences or fix wording; if a source has nothing relevant, skip it; if you find fewer than {minimum} findings, return them anyway and set "enough": false.
After a code step removes any quote that isn't found on its page, a second prompt will write the report from the remaining findings only.

Inspired by u/Fit-Appointment700 on r/n8n: Three workflows where code checks the model's quotes before showing them. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Pages change and some block fetching; log failures separately from 'quote not found' so you can tell them apart.
  • A real quote can still be taken out of context. Spot-check a few against the full page.

Our take

This post states a principle every research automation should borrow: let the model suggest, and let code decide what reaches the reader. Language models are good at finding and summarizing material and bad at guaranteeing a quote is real, so asking for the exact sentence and the page it came from, then checking that sentence against the fetched page, removes the most embarrassing failure. The three examples cover common business needs well: a cited research brief, an article whose statistics have gone stale, and a list of software alternatives that doesn't let vendors vote for themselves. The rule to admit when too little checks out, rather than filling in from memory, matters just as much; an automation that admits it found too little is far safer than one that fills gaps. Our version separates the quote-gathering prompt from the writing step, so the writer sees only verified material. In our dry run with five made-up source pages and a question about remote-work productivity, the model returned 9 quotes; a simple exact-match check passed 6, caught 2 paraphrases presented as quotes and 1 quote attributed to the wrong page, and the summary used only the 6.

Where the time goes back: Fact-checking every citation by hand is replaced by a code check, and you only read the items that passed.

FAQ

Why not ask the model to double-check itself?
A model checking its own quotes can repeat the same mistake. A few lines of code that search the page text give a yes or no answer it can't argue with.
Is the workflow available?
The poster published the workflow files on GitHub and in n8n's template library; the original post links them.

Source and credit

Inspired by u/Fit-Appointment700 on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Three workflows where code checks the model's quotes before showing them
Creator
u/Fit-Appointment700 on r/n8n
Published on
Reddit
Original date
Oct 19, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Quote-or-drop rule worked; the writer saw only verified material.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingWorkflow✓ AI dry run

Keep AI steps in an n8n content workflow from breaking

Build an n8n article pipeline from small single-purpose AI steps (brief, outline, section writing, page metadata), require structured JSON from each, check every output before it moves on, retry and alert on failures, publish as a draft for a human look, and run the lighter steps on a less expensive model.

Credit: Amin_Mahmodi

An afternoon+
MarketingPrompt✓ AI dry run

Explain a business process with a short animated walkthrough

Turn the documents that describe one of your processes into a short, vertical animated explainer for investors, new hires or clients, with every on-screen claim traced back to a file.

Credit: Avi Hacker, J.D.

Under an hour
MarketingSkill✓ AI dry run

Make an AI-built screen look designed with the unslop skill

Install Damir Sokolovsky's open unslop skill in Claude Code or Codex, point it at a dashboard, app screen, landing page or even a live URL, approve the short design direction it proposes from your product, and let it fix the screen in nine ordered passes, stopping early if the screen is already good.

Credit: Damir Sokolovsky (@heydamir)

Minutes
MarketingWorkflow✓ AI dry run

Get a daily blog health report from a scoped bot role

Receive a dated report each morning confirming the scheduled post went live, comparing traffic, listing top pages and checking the last deploy, with every claim sourced.

Credit: Flavio Copes

Under an hour
MarketingWorkflow✓ AI dry run

Replace a failing content agent with a fixed workflow

Stop cleaning up invented stats and blended sources by running the same proven content steps every time, with AI used only at chosen points.

Credit: Wyndo

An afternoon+