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?
- 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.
- Check in codeFetch the page and test whether the quoted sentence is really there, after normalizing spaces and quote marks. Drop anything that fails.
- Set a floorIf fewer than a set number of findings survive, report that instead of writing anyway.
- 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)
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?
Is the workflow available?
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
- 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.