Seo blog content automation with GPT-4o-mini and human approval in Google Docs
Overview
This n8n workflow automates the entire content creation process for SEO blog posts, from topic submission and AI drafting to human approval, revision, and final storage in Google Docs. It ensures high-quality, SEO-optimized content is generated efficiently while keeping a human in the loop for quality control.
Prerequisites
To use this workflow, you need the following accounts and credentials:
Google Sheets Account:
To manage the content tracker. The sheet must contain columns for Topic, Reference URL, Title, Status, and Link to document.
OpenAI API Key (for GPT-4o-mini):
To power the initial content drafting and subsequent revisions.
Gmail Account:
To send the content for human approval and wait for feedback.
Google Docs Account:
To create and store the final approved blog posts.
How It Works
The workflow operates in four main stages: Topic Submission, AI Content Creation, Human Approval & Revision Loop, and Final Publishing.
Stage 1: Topic Submission and Tracking
This stage captures a new blog topic and adds it to the content tracker.
On form submission (Form Trigger): The workflow is initiated when a user submits a Topic and an optional Reference link through the form.
Append row in sheet (Google Sheets): The new topic and reference link are added as a new row in your content tracker sheet.
Get Topic from Google Sheets: The workflow fetches the newly added row, including the system-generated row_number for tracking updates.
Stage 2: AI Content Creation (Initial Draft)
The workflow uses an expert AI agent to generate the first draft of the blog post.
Copywriter AI Agent: Acting as an expert SEO content strategist, the agent receives the topic and reference URL.
The agent improves the provided topic into an SEO-optimized title.
It writes a complete, conversational, SEO-friendly blog post (800β1200 words) using proper Markdown headings and lists.
OpenAI Chat Model (GPT-4o-mini): Powers the agent's generation.
Structured Output Parser: Ensures the output is in a JSON format with separate title and content keys.
Set Data: The AI-generated title and content are mapped to workflow variables (Topic Title, Content) for easy use in subsequent nodes.
Stage 3: Human Approval and Revision Loop
This is the critical quality control step where a human reviews the draft and decides on the next action.
Send Content for Approval (Gmail): The generated title and content are sent via email to the approver (<your email>).
This uses a custom form that allows the user to choose Yes (Approve), No (Request Revision), or Cancel. The form also includes a Content Feedback textarea.
Approval Result (Switch): The workflow pauses until the approver submits the form, and then directs the flow based on their choice.
If "Yes" (Approved): Proceeds to the final publishing stage. The Update Topic Status on Google Sheets node is executed, setting the Status to Approved and logging the new Title.
If "No" (Revision Requested): Proceeds to the revision loop.
Copywriter Revision Agent: This agent takes the original content, the topic title, and the user's Content Feedback. It is instructed to incorporate the feedback, preserving the existing structure and tone, and outputs a revised blog post.
The flow loops back through the Set Data node and then returns to the Send Content for Approval node for a new review.
If "Cancel": Stops the workflow, and the Update Topic Status on Google Sheets node is executed.
Stage 4: Final Publishing
Once approved, the content is stored in Google Docs and the tracker is updated.
Create Blog file (Google Docs): A new Google Doc is created using the approved Topic Title.
Add blog content in file (Google Docs): The final Content (in Markdown format) is inserted into the newly created document.
Update sheet with blog post link (Google Sheets): The final tracker update logs the Link to document and the Published date.
Customization Tip
Recommend using AI humanazier and AI detector tools before approval to make the SEO score better.
SEO Blog Content Automation with GPT-4o Mini and Human Approval in Google Docs
This n8n workflow automates the generation of SEO-optimized blog content using AI, integrating human approval via email, and managing content in Google Sheets and Google Docs. It streamlines the content creation process from topic ideation to draft generation and finalization.
What it does
This workflow simplifies and accelerates the creation of blog content by:
- Triggering Content Generation: Initiates the workflow when a new blog topic request is submitted via an n8n form.
- Preparing Data: Extracts and formats the blog topic from the form submission.
- Generating Blog Content with AI: Uses an OpenAI Chat Model (GPT-4o Mini) and a LangChain AI Agent to generate a blog post draft based on the provided topic. It includes a structured output parser to ensure the AI output adheres to a predefined format (e.g., title, sections, content).
- Creating a Google Doc: Automatically creates a new Google Doc with the generated blog post draft.
- Requesting Human Approval: Sends an email via Gmail to a designated approver, containing the link to the Google Doc draft and options to approve or reject the content.
- Handling Approval/Rejection:
- If approved, the workflow could proceed to a "publish" step (not fully implemented in this JSON, but implied by the "Approved" branch).
- If rejected, the workflow could notify the content team or loop back for revisions (not fully implemented in this JSON, but implied by the "Rejected" branch).
- Logging: (Implied, often a next step for approved content) Update a Google Sheet with the status of the content.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Account: A running instance of n8n.
- OpenAI API Key: For the OpenAI Chat Model (GPT-4o Mini).
- Google Account: With access to Google Sheets and Google Docs for content management.
- Gmail Account: For sending approval emails.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- OpenAI: Set up your OpenAI API key credential.
- Google: Configure your Google OAuth2 credentials for Google Sheets, Google Docs, and Gmail. Ensure the necessary scopes are granted for reading/writing to Sheets and Docs, and sending emails.
- Configure the n8n Form Trigger:
- Activate the "On form submission" trigger node.
- Share the form URL with your content requesters. The form should ideally have a field for the blog topic.
- Customize AI Agent and Output Parser:
- Review the "AI Agent" node and "Structured Output Parser" node. You may want to adjust the prompts, tools, and the JSON schema in the output parser to match your specific content requirements and desired output format.
- Set Approval Email Details:
- In the "Gmail" node, specify the recipient email address for approvals, and customize the email subject and body as needed. Ensure the Google Doc link is correctly embedded.
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow.
Now, whenever a new form submission is received, the workflow will automatically generate a blog draft, create a Google Doc, and send an approval email.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack
AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. ποΈπ€π Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (β€3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | π Professional Services Need help with implementation or customization? Our team offers: π― Custom workflow development π’ Enterprise deployment support π Team training sessions π§ Ongoing maintenance π Custom reporting & dashboards π Additional API integrations Discover more workflows β Get in touch with us