Why AI Companies Are Destroying Rare Books—and How Your Business Can Build a Better Data Moat with n8n

The Rare-Book Signal

This week, a Reddit thread on r/artificial described something that should stop every ops leader, agency owner, and clinic operator cold. AI companies are buying antique books, ingesting their contents to train models, and then destroying them at incredible scale—even if almost no copies remain. The post is a reminder that the biggest bottleneck in AI is no longer compute. It's data.

At the same time, over on r/n8n, someone shared their first workflow and asked for feedback. It was the kind of post that usually doesn't go anywhere—a beginner showing off a small automation. But read those two signals side by side and you get a clear picture: the market is desperate for unique, high-quality data, while most businesses are still treating their operational data like old furniture.

As an automation engineer, I see this gap every day. B2B service teams run on CRM notes, call transcripts, email threads, and project updates. Clinic operators sit on intake forms, follow-up logs, and outcome data. Agencies have onboarding calls, client feedback, and delivery playbooks. That is the exact kind of proprietary, hard-to-replicate data AI companies are literally destroying printed books to obtain.

You don't need to burn anything to build your own data asset. You need an automation pipeline that captures, cleans, and structures the knowledge already flowing through your business. n8n is the right tool for that job.

The Problem

The antique book story is extreme, but it makes a larger point: AI training data is becoming scarce. Public text has been scraped to the point of diminishing returns. Companies are now turning to physical archives, private collections, and other atoms because the bytes have been picked clean. If an AI company will pay to destroy a rare book just to ingest its sentences, imagine how much value they place on data that isn't publicly available.

The problem is that most businesses have the opposite posture. Their valuable data is trapped in tools designed for human consumption, not machine use. A clinic's patient notes are in a PDF in a folder. An agency's best onboarding lessons are in a Slack thread. An ops leader's vendor evaluation criteria are in an email chain. None of that is usable for training a model, building an AI voice agent, or making an internal assistant smarter. It's just dead weight.

That's where n8n comes in. It is an automation platform that can connect CRMs like GoHighLevel, databases, email, forms, and AI models. It lets you turn messy operational noise into structured, searchable, AI-ready data. And unlike the antique book approach, you can do it without destroying anything.

The Solution

Think of this as building a data moat. A moat is a defensible advantage that competitors can't easily copy. For a B2B service team, that is not your tool stack. It's not your website copy. It's the accumulated knowledge of how you solve problems for real clients. The same is true for clinic operators and agency owners: the way you handle edge cases is your intellectual property.

The playbook is simple:

1. Pick one high-value data source.
2. Build an n8n workflow that captures it automatically.
3. Clean and structure it with AI.
4. Store it somewhere queryable.
5. Use it to improve your AI agent, your team, or your client deliverables.

You don't need to boil the ocean. Start with one workflow, like the person in the r/n8n thread did. Their first workflow probably moved a row from a spreadsheet into a Slack message or generated a custom response. That's fine. The important part is that they started. You can start too, but with a bigger target: your own training data.

Implementation

Let me walk you through the workflow I recommend to clients who are serious about this. I'll keep it tool-agnostic because the exact nodes depend on your stack, but the pattern is the same.

Step 1: Choose a source of truth

Do not try to capture everything. Pick one source with high signal density.

• Agency owner: onboarding call transcripts or project kickoff notes.
• Clinic operator: patient intake forms or follow-up call summaries.
• Ops leader: ticket resolutions or vendor email threads.

For B2B service teams, my default is call transcripts from AI voice agents or recorded sales calls. They contain objections, tone, questions, and successful resolutions. That's gold.

Step 2: Create an n8n trigger

In n8n, create a new workflow. Add a trigger that fires when a new item appears in that source.

• If you use GoHighLevel, use the 'Contact Created' or 'Opportunity Updated' trigger.
• If you use a form, use the webhook trigger and point your form at it.
• If you use email, use the Gmail/Outlook trigger.

The r/n8n first workflow thread is a good reminder that you don't need a perfect architecture on day one. You need a trigger, an action, and a place to put the result. Start there.

Step 3: Normalize the data

This is the step most people skip. Raw data is messy. A call transcript has filler words. A patient note has inconsistent abbreviations. A ticket has duplicate context.

Add an n8n Code node or an OpenAI/Anthropic node to clean the data. Give the AI a system prompt that says, 'Extract the following fields: topic, decision, next step, owner, sentiment.' Then output JSON.

For example, if you're a clinic operator, you might extract:

• patient concern
• recommended action
• follow-up interval
• staff member assigned

If you're an agency owner, extract:

• client objection
• proposed solution
• approved or not
• risks mentioned

This is where you turn text into structured knowledge. It's the same 'ingestion' AI companies are doing with antique books—except you're doing it with your own living documents, and you're not destroying anything.

Step 4: Store it in a queryable format

Send the normalized JSON to a database, Google Sheet, Airtable, Notion, or even a simple file in S3. The key is to make it easy to search later.

For a client with an existing data warehouse, use Postgres or BigQuery. For smaller teams, Google Sheets is honestly fine at the start. You can query it with n8n later or connect it to an AI tool for retrieval-augmented generation (RAG). The storage layer matters less than the discipline of actually storing it.

Step 5: Activate the data

Once you have a few hundred structured records, you can do something useful with them:

• Fine-tune a small model on your own tone and decisions.
• Build a RAG pipeline that helps your AI voice agent answer client questions based on what actually worked before.
• Create an internal assistant for your team that knows how you handle edge cases.

This is the difference between using AI as a generic chatbot and having an AI that understands your business. This is also the part that separates you from every competitor who is still using ChatGPT in a browser tab.

Results

I don't have a chart for you because the results depend on how consistent you are. But the qualitative shift is clear. Instead of relying on public data that AI companies are scraping into oblivion, you're building a proprietary dataset that makes your automations sharper.

The n8n beginner in that Reddit thread will learn more in their first week than someone who just reads about AI. But the real win comes when you point those workflows at the knowledge your business produces every day. You stop being a consumer of generic AI and start being a producer of specific AI.

Key Takeaways

• AI companies are so desperate for unique data that they are destroying rare books. Your private operational data is more valuable than you think.
• Start small. Build one n8n workflow that captures a single high-value data source.
• Normalize everything with AI into structured JSON before storing it.
• Use that structured data to train, fine-tune, or ground your AI voice agents and internal tools.
• Don't wait until your data is public or irrelevant. The time to build your data moat is now.

Sources

• AI Companies Are Buying Antique Books, Ingesting Their Contents to Train Models, and Then Destroying Them at Incredible Scale, Even If Almost No Copies Remain
• My first n8n workflow. I'd appreciate your feedback.