Automate Content Improvement with n8n and Markup AI

Ever wished you could automate content improvement by checking every document in your workflow — and even get a cleaned-up version back — without asking an editor to touch it?

That’s exactly what you can do with Markup AI inside n8n. In this blog post, we’ll walk through two plug-and-play workflows:

1. One that checks and scores your content.
   
2. One that rewrites it and delivers a polished version to your inbox.

Key takeaways

• Manual reviews don’t scale: Relying on human editors for every doc, PDF, or markdown file creates bottlenecks and makes it easy for low-quality content to slip through.
  
• Let n8n orchestrate, Markup AI analyze: Use n8n to pull content from any source and send it to Markup AI for automated quality checks or rewrites.
  
• Workflow #1 – Quality Gate: Build a simple flow that fetches a document, sends it to Markup AI for analysis, and emails you a full quality report with scores.
  
• Workflow #2 – Auto-Rewrite: Extend the same flow so Markup AI rewrites the content and Gmail sends the improved version directly to your team.
  
• Source-agnostic by design: Google Drive is just the example — the Markup AI node in n8n works with any integration n8n supports (CMSs, storage, APIs, tickets, forms, and more).

Why automate content improvement in the first place?

Most teams know the feeling:

• Editors are overloaded, working through backlogs and trying not to miss anything.

• Content lives everywhere — drives, CMSs, tickets, emails, uploads.

• Different people contribute with different levels of writing expertise.

The result? Inconsistent tone, unclear content, grammar mistakes, and terminology issues — all of which directly impact credibility, support efficiency, and user experience.

Markup AI + n8n turns this into a continuous, automated quality layer:

• n8n connects to your existing tools.
  
• Markup AI scores and (optionally) rewrites content.

You get alerts or improved versions without manual review.

Instead of hoping someone catches issues after the fact, you bake quality into your workflow by design. That means content is reviewed the moment it’s created or updated, not days later when it’s already been shared, published, or acted on.

How Markup AI fits into n8n

At its core, the Markup AI node in n8n is a content-quality engine:

• It accepts content from any upstream node (Google Drive, HTTP, CMS, email, forms, etc.).
  
• It runs a Style Check or a Style Rewrite based on your configuration.
  
• It returns structured data: Scores, issue counts, clarity metrics, tone analysis — and, if enabled, a rewritten version of the content.

Because n8n is integration-first, you’re not tied to any one source. Google Drive is a great quickstart example, but you can easily swap it out for:

• Your CMS
  
• Cloud storage
  
• A support system
  
• A database
  
• A webhook that delivers content from anywhere

Let’s look at the two workflows that show this value clearly.

Workflow #1 – Quality gate: Score and report every document

Problem this solves:
You want to know if your content meets your standards; without manually reading every file.

What this workflow does:

1. Trigger: Start the workflow when a document is created or updated.
   
   • Example: A file is added/changed in a specific Google Drive folder.
     
   • In production, this could just as easily be a CMS publish event, an API call, or a scheduled run.
     
2. Retrieve the document:
   
   • Use the relevant n8n node (e.g., Google Drive) to download the file.
     
3. Extract the text:
   
   • If it’s a PDF or binary format, use an Extract from File node.
     
   • If it’s markdown, HTML, or plain text, you can pull the body directly.
     
   • The end goal is a single text field (for example, data) containing the content.
     
4. Analyze with Markup AI (Style Check):
   
   • Add the Markup AI node.
     
   • Set it to run a Style Check on the extracted text.
     
   • Configure your style guide, tone, and other preferences.
     
5. Markup AI returns structured scores and metrics like:
   
   • score (overall quality)
     
   • grammar.score, grammar.issues
     
   • consistency.score, consistency.issues

   • terminology.score, terminology.issues

   • analysis.clarity.score, readability metrics

   • analysis.tone.score, tone alignment

6. Send an email with the scores:
   
   • Use a Gmail (or any email) node to send a digest of the results.
     
   • Include the main scores and issue counts in the body so reviewers instantly understand the state of the content.
     

What you end up with:
A hands-off automated quality gate. Every time a document changes, your team receives a quality report with objective scores and specific issue counts — without opening the original file.

You can take it further by adding an IF node:

• If score < 70 → mark as “needs review” or notify an editor.
  
• If grammar.issues > 10 → automatically create a task in your PM tool.
  

But even the basic version already replaces hours of manual scanning.

Download the n8n workflow JSON

Want to try this workflow without building it from scratch?
You can download the ready-made n8n workflow JSON and import it directly into your own instance.

This template includes:

• Trigger → file change in a Google Drive folder
  
• File download + text extraction
  
• Markup AI Style Check node
  
• Gmail node that sends a quality report with scores

How to use it:

1. Activate the workflow and drop a file into your folder to see it in action.
2. Download the JSON file.
3. In n8n, go to Workflows → Create a Workflow → Import from File.
4. Add your own credentials (Google Drive, Markup AI, Gmail).

Donwload: Workflow #1 – Quality Gate: Score and report every document JSON file.

Workflow #2 – Auto-rewrite: Get a cleaned-up version in your inbox

Problem this solves:
You don’t just want to know what’s wrong; you want a fixed version you can use directly — without manually editing the content.

This is where the Style Rewrite operation shines.

What this workflow does:

1. Same first steps as Workflow #1:
   
   • Trigger on doc creation/update.
     
   • Retrieve the file.
     
   • Extract the text into a single field (e.g., data).
     
2. Analyze and rewrite with Markup AI:
   
   • Use the Markup AI node, but select Style Rewrite instead of just a check.
     
   • Provide the same settings: style guide, tone, etc.
     
   • Markup AI returns:
     
     • The same scores and analysis as before, plus…
       
     • A rewritten version of the text (for example, rewrite.text).
       
3. Turn the rewritten text into something usable:
   You have several options here, depending on your workflow:
   
   • Attach it as a text file using a “Convert to File” node.
     
   • Inject it back into a CMS via an HTTP Request node.
     
   • Save it in cloud storage.
     
   • Or keep it simple: send it directly in an email.
     
4. Send the rewritten version via email:
   
   • With a Gmail node, you can send an email that:
     
     • Includes the core scores (so the recipient understands why changes were made).
       
     • Attaches the rewritten file or includes the rewritten text in the body.
       

What you end up with:
An auto-editing pipeline. Whenever content lands in your system, your team receives a polished, brand-aligned version and the underlying scores. Editors can focus on nuance and strategy instead of fixing commas, tone, or basic clarity.

Download the n8n workflow JSON

If you’d rather receive a cleaned-up version of your content automatically, you can use our Auto-Rewrite workflow as a starting point.

This template includes:

• Trigger → file change in a Google Drive folder
  
• File download + text extraction
  
• Markup AI Style Rewrite node
  
• Gmail node that sends the rewritten version (plus scores) to your inbox

How to use it:

Activate the workflow and upload a document to receive an instant rewritten version.

1. Download the JSON file.
2. In n8n, go to Workflows → Create a Workflow → Import from File.
3. Plug in your own credentials (Google Drive, Markup AI, Gmail).
4. Activate the workflow and upload a document to receive an instant rewritten version.

Donwload: Workflow #2 – Auto-Rewrite: Get a cleaned-up version in your inbox JSON file.

Which workflow should you choose?

Both workflows use the same core pieces: source → extract text → Markup AI → email. The difference is in what you want as an outcome.

Use Workflow #1 – Quality Gate when you want to:

• Keep your existing writing process but add automated oversight.
  
• Have editors or owners decide what to change — using scores and issue lists as guidance.
  
• Build dashboards and KPIs around content quality over time.

Use Workflow #2 – Auto-Rewrite when you want to:

• Reduce editing time by sending a ready-to-use version directly to stakeholders.
  
• Standardize voice, terminology, and style faster across large teams.
  
• Help subject-matter experts (who aren’t writers) produce publishable content.

Many teams start with Workflow #1, then add Workflow #2 for specific use cases (like blog drafts, internal docs, or support content).

Why this works so well with n8n?

The Markup AI node isn’t tied to Google Drive. That’s just the fastest demo.

Because n8n is integration-first, you can:

• Swap Google Drive for your CMS, CRM, forms, support system, or file storage.
  
• Replace Gmail with Slack, Teams, a database, or any other integration.
  
• Trigger workflows from webhooks, schedules, or events instead of just file changes.

In other words, Markup AI becomes a reusable quality and rewriting component inside your automation stack — wherever content flows, you can drop this node in.

Get started in a few steps

Here’s a simple way to get value quickly:

1. Connect Markup AI to n8n
   
   • Add your Markup AI API key as credentials.
     
2. Build Workflow #1 (Quality Gate)
   
   • Trigger → Retrieve content → Extract text → Markup AI (Style Check) → Gmail with scores.
     
3. Test with real documents
   
   • Drop a few PDFs or docs into your monitored source and check the email reports.
     
4. Add thresholds and conditions
   
   • Use the scores (score, grammar.score, analysis.clarity.score, etc.) in IF nodes.
     
5. Upgrade to Workflow #2 (Auto-Rewrite)
   
   • Switch the Markup AI node to Style Rewrite.
     
   • Attach or deliver rewrite.text to your stakeholders.

In less than an afternoon, you can move from “we hope our content is good enough” to “every document is checked or rewritten before anyone sees it.”

Take the next step

Content quality shouldn’t depend on who happens to be available to review a document on a given day. As content volume and velocity grow, you need systems, not heroic copyediting.

By combining Markup AI with n8n, you automate content improvement by turning your workflows into always-on Content Guardians — scoring, rewriting, and flagging content 24/7, across all the tools you already use.

Don’t let low-quality content quietly erode your brand, confuse your users, or slow down your teams. Start with one simple workflow — a quality gate or an auto-rewrite flow — and expand from there.

Your stack already knows how to move files around. With Markup AI in n8n, it will finally know what’s inside them — and how to make them better.