Validate newsletter quality with GPT-5 quality gate before sending

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Newsletter Quality Assurance with LLM Judge This sub workflow validates newsletter quality before sending to customers. It's triggered by the main newsletter workflow and acts as an automated quali...

Best for

Social Media automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.gmail, n8n-nodes-base.wait, n8n-nodes-base.set, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.outputparserstructured

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Emir Belkahia.

Original n8n.io source

1.1 Workflow description

Title: Validate newsletter quality with GPT-5 quality gate before sending
Workflow name: Validate newsletter quality with GPT-5 quality gate before sending

Newsletter Quality Assurance with LLM Judge

This sub-workflow validates newsletter quality before sending to customers. It's triggered by the main newsletter workflow and acts as an automated quality gate to catch data issues, broken layouts, or missing content.

Who's it for

E-commerce teams who want to automate newsletter quality checks and prevent broken or incomplete emails from reaching customers. Perfect for ensuring consistent brand quality without manual review.

How it works

Receives newsletter HTML - Triggered by parent workflow with the generated newsletter content
Sends to test inbox - Delivers newsletter to LLM Judge's Gmail inbox to validate actual rendering
Retrieves rendered email - Fetches the email back from Gmail to analyze how it actually renders (catches Gmail-specific issues)
AI-powered validation - GPT-5 analyzes the newsletter against quality criteria:
- Verifies all 6 product cards have images, prices, and descriptions
- Checks layout integrity and date range formatting
- Detects broken images or unprocessed template variables
- Validates sale prices are lower than original prices
Decision gate - Based on Judge's verdict:
- PASS: Returns approval to parent workflow → sends to customers
- BLOCK: Alerts admin via email → requires human review

Set up steps

Setup time: ~5 minutes

Connect your Gmail account for sending test emails
Update the Judge's email address in "Send newsletter to LLM Judge" node
Update the admin alert email in error handling nodes
Connect your OpenAI API credentials (GPT-5 recommended for heavy HTML processing)
(Optional) Adjust quality thresholds in the Judge's system prompt

Requirements

Gmail account for test sends and retrieving rendered emails
OpenAI API key (GPT-5 recommended)
Parent workflow that passes newsletter HTML content

How to customize

Adjust validation strictness: Modify the Judge's system prompt to change what triggers BLOCK vs PASS
Change product count: Update prompt if your newsletters have different numbers of products
Add custom checks: Extend the system prompt with brand-specific validation rules
Modify alert recipients: Update email addresses in error handling nodes

💡 Pro tip: The workflow validates the actual Gmail-rendered version to catch image loading issues and ensure consistent customer experience.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Sticky Note9

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Sticky Note11

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Sticky Note12

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Send newsletter to LLM Judge

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 6 - Get the newsletter

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 7 - Give the email some time to arrive

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 8 - Simplify output before giving to Agent

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 9 - Inform human that there are errors

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 10 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 11 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 12 - Judge happy ?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 13 - Send approval to parent workflow

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 14 - Judge 👩‍⚖️

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3

Block 15 - GPT5 as the input to review is heavy

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices: Version 1.3

Block 16 - Expected Format

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 17 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 18 - Sticky Note13

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Ask Human to review Newsletter

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 22 - Executed from Newsletter Creation workflow

Type / Role: n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices: Version 1.1

3. Summary Table

Workflow	Validate newsletter quality with GPT-5 quality gate before sending
Complexity	advanced
Nodes	22
Categories	Social Media, AI Summarization
Author	Emir Belkahia
Published	11 Nov 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/10734/10734.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Social Media workflows AI Summarization workflows

Frequently asked questions

What does Validate newsletter quality with GPT-5 quality gate before sending do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media, AI Summarization use case.

Emir Belkahia

5 workflows

Nodes

n8n-nodes-base.stickynote n8n-nodes-base.gmail n8n-nodes-base.wait n8n-nodes-base.set n8n-nodes-base.if @n8n/n8n-nodes-langchain.agent @n8n/n8n-nodes-langchain.lmchatopenai @n8n/n8n-nodes-langchain.outputparserstructured

Complexity

advanced

Published 11 Nov 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/10734/10734.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Promote YouTube uploads to social channels with DeepSeek and Posta

## Quick overview This workflow fetches the latest video from a YouTube channel feed, generates platform-specific promo captions with DeepSeek, and creates draft promotion posts in Posta for active social media accounts. You can automatically promote your videos to all your social media. Add a "publish" at the end for auto-post. ## How it works 1. Runs manually when you click “Execute workflow”. 2. Fetches your YouTube channel RSS feed over HTTP, parses the XML, and extracts the latest video’s title, description, thumbnail URL, and link. 3. Downloads the video thumbnail and uploads it to Posta to create a reusable media asset. 4. Retrieves your social accounts from Posta, keeps only active accounts, and de-duplicates them to one account per platform. 5. Combines the latest video data with each target platform and asks DeepSeek (via an n8n LangChain LLM chain) to write a tailored promotional caption per platform. 6. Tags each generated caption with its platform and merges it back to the matching Posta social account. 7. Creates a draft Posta post per selected account, attaching the uploaded thumbnail and the platform-specific caption and video link. 8. (Optional) Add a "publish a post" at the end to automatically post to the social media channels (If you are feeling brave and trust the LLM), ## Setup 1. Add a Posta API credential and select it in the Posta nodes that list accounts, upload media, and create posts. 2. Add a DeepSeek API credential and select it in the DeepSeek Chat Model node. 3. Update the YouTube channel feed URL (channel_id) in the HTTP request that downloads the YouTube feed. 4. Review your Posta social accounts to ensure the intended accounts are marked active and have the correct platform values for de-duplication. ## Additional info Video explanation: https://youtu.be/tTWaYb71YyA

View

Post scheduled Threads updates from Google Sheets with error tracking

## Quick overview This workflow runs hourly to read the next pending post from Google Sheets, publishes it to Threads via the Threads Graph API, and then updates the sheet with published or failed status plus timestamps and error details. ## How it works 1. Runs every hour on a schedule. 2. Reads the first row in Google Sheets where the status column equals pending. 3. Retrieves the authenticated Threads account’s user ID from the Threads Graph API. 4. Creates a Threads text post container using the content from the pending Google Sheets row. 5. Publishes the post to Threads and updates the same Google Sheets row as published with posted_at and updated_at timestamps. 6. If any Threads API call fails, records the error message and marks the corresponding Google Sheets row as failed with an updated_at timestamp. ## Setup 1. Create a Meta app and generate a Threads access token, then add it to an HTTP Header Auth credential used for the Threads Graph API requests. 2. Set up a Google Sheets Service Account credential in n8n and share your target spreadsheet with the service account email. 3. Replace the placeholder Google Sheet ID in all Google Sheets nodes and confirm the sheet name is Sheet1 (or update it to match your sheet). 4. Ensure your sheet has the required columns (row_number, content, status, posted_at, updated_at, error_message) and set status to pending for posts you want published.

View

Send a daily product newsletter with Google Sheets and Gmail

## Quick Overview This workflow runs daily at 08:00, pulls products scheduled for today from Google Sheets, generates an HTML newsletter email, and sends it to each subscriber via Gmail. ## How it works 1. Runs every day at 08:00 on a schedule. 2. Reads all rows from the `newsletter_products` sheet in Google Sheets. 3. Keeps only products whose `send_date` matches today’s date and stops if none are found. 4. Builds an HTML email and subject line containing a card for each product (image, description, and optional referral link). 5. Reads the subscriber list from the `newsletter_recipients` sheet in Google Sheets. 6. Sends the generated newsletter to each recipient individually using Gmail. ## Setup 1. Create or copy a Google Sheets document with `newsletter_products` (including a `send_date` column) and `newsletter_recipients` (including an `email` column). 2. Add a Google Sheets OAuth2 credential in n8n and paste your Google Sheet ID into the Config step. 3. Add a Gmail OAuth2 credential and confirm the sender mailbox to use for sending the newsletter. 4. Add products and recipients to the sheet, run a test execution, and adjust the schedule/timezone if needed before activating.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Validate newsletter quality with GPT-5 quality gate before sending

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Newsletter Quality Assurance with LLM Judge

Who's it for

How it works

Set up steps

Requirements

How to customize

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Sticky Note2

Block 2 - Sticky Note9

Block 3 - Sticky Note11

Block 4 - Sticky Note12

Block 5 - Send newsletter to LLM Judge

Block 6 - Get the newsletter

Block 7 - Give the email some time to arrive

Block 8 - Simplify output before giving to Agent

Block 9 - Inform human that there are errors

Block 10 - Sticky Note

Block 11 - Sticky Note1

Block 12 - Judge happy ?

Block 13 - Send approval to parent workflow

Block 14 - Judge 👩‍⚖️

Block 15 - GPT5 as the input to review is heavy

Block 16 - Expected Format

Block 17 - Sticky Note3

Block 18 - Sticky Note13

Block 19 - Sticky Note4

Block 20 - Sticky Note5

Block 21 - Ask Human to review Newsletter

Block 22 - Executed from Newsletter Creation workflow

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions