HumationHuman + Automation
Back to Catalog

Automate content publishing with GPT-4 via Google Sheets to email & Slack approval

Rahul JoshiRahul Joshi
115 views
2/3/2026
RetryUser ManagementWebhookError HandlingAPI
Official Page

Streamline the final stage of your content production workflow by automating publishing, formatting, metadata generation, and approval routing. This AI-powered subworkflow pulls optimized drafts from Google Sheets, enriches them with SEO metadata, converts them into publish-ready HTML, and delivers them via email and Slack for approval or distribution. Ideal for teams managing high-volume content pipelines with structured review processes. ✨📝🚀

What This Template Does

  • Triggers via chat to start the content publishing process. 💬
  • Fetches the latest optimized content draft from Google Sheets using a content ID. 📄
  • Prepares metadata such as topic, intent, platform, and parameters. 🧩
  • Uses an AI agent (GPT-4) to generate SEO metadata, HTML-formatted article, tags, and structured publish data. 🤖
  • Enforces JSON structure to ensure consistent output formatting. 🧱
  • Saves the publish-ready content (title, meta description, HTML, tags) back into Google Sheets for version tracking. 📊
  • Sends the content to an approver via Gmail with a previewed HTML body. 📧
  • Awaits approval and branches based on decision. 🔀
  • If approved, sends the final published content to the intended recipient via Gmail. 📨
  • Sends a success confirmation message to Slack for team visibility. 📢

Key Benefits

✅ AI-generated SEO optimization, metadata, and HTML formatting ✅ Centralizes content versioning within Google Sheets ✅ Automates approval workflows and content delivery ✅ Ensures consistent output structure with JSON parsing ✅ Reduces manual formatting, editing, and routing tasks ✅ Delivers instant Slack notifications for team transparency

Features

  • Chat-triggered publishing workflow
  • Google Sheets content retrieval and storage
  • AI-driven formatting, metadata generation, HTML conversion
  • Structured JSON enforcement for clean automation
  • Gmail integration for approval + publishing
  • Slack notifications for successful publication
  • Short-term memory support for context persistence

Requirements

  1. Google Sheets OAuth2 credentials
  2. OpenAI API key (GPT-4 or GPT-4 mini)
  3. Gmail OAuth2 credentials for sending and receiving approval messages
  4. Slack API credentials with chat:write access
  5. Preconfigured Google Sheet containing optimized content drafts

Target Audience

  1. Content operations teams handling recurring content workflows
  2. SEO and marketing teams producing high-volume articles
  3. Agencies managing structured approval pipelines
  4. Automation specialists building content publishing systems
  5. Teams needing standardized, AI-enhanced HTML content

Step-by-Step Setup Instructions

  • Connect your Google Sheets OAuth2 credential and replace the sheet/document IDs. 🗂️
  • Add your OpenAI API key for the AI Publishing Agent. 🔑
  • Connect Gmail credentials for both approval and final publishing emails. 📧
  • Update all email addresses and Slack channel IDs with your own. ✏️
  • Modify metadata fields (topic, intent, platform) if needed. 🎯
  • Run the workflow with a sample content ID to verify the flow. 🔍
  • Enable and integrate as a subworkflow inside your main content pipeline. 🚀

Automate Content Publishing with GPT-4 via Google Sheets to Email & Slack Approval

This n8n workflow automates the process of generating content using GPT-4, publishing it, and managing approval via Slack and email. It acts as a content creation and distribution pipeline, ensuring content is reviewed before being sent out.

What it does

This workflow streamlines your content publishing process through the following steps:

  1. Listens for Chat Messages: The workflow is triggered when a chat message is received, likely initiating a content generation request.
  2. Generates Content with AI Agent: An AI Agent (configured with an OpenAI Chat Model and Simple Memory) processes the chat input to generate content.
  3. Parses AI Output: A Structured Output Parser extracts relevant data from the AI-generated content.
  4. Edits Fields: The extracted data is then processed and formatted using an "Edit Fields" (Set) node.
  5. Conditional Approval: An "If" node checks a condition (e.g., if approval is required or if certain criteria are met).
    • If True (Approval Needed): The content is sent for approval via a Slack message and an email (using Gmail).
    • If False (No Approval Needed): The content is directly published (though the publishing step itself is not explicitly defined in the provided JSON, it would typically follow this branch).
  6. Records to Google Sheets: Regardless of the approval path, the content details are recorded in a Google Sheet for tracking and record-keeping.
  7. Provides Notes: A Sticky Note is included for documenting specific instructions or information within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: For the OpenAI Chat Model to generate content using GPT-4.
  • Google Sheets Account: To store and retrieve content data.
  • Slack Account: For sending approval requests.
  • Gmail Account: For sending approval requests via email.
  • LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed and enabled in your n8n instance, as it's used for the AI Agent, OpenAI Chat Model, Simple Memory, Structured Output Parser, and Chat Trigger.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI API Key credential for the "OpenAI Chat Model" node.
    • Configure your Google Sheets credential for the "Google Sheets" node.
    • Set up your Slack credential for the "Slack" node.
    • Configure your Gmail credential for the "Gmail" node.
  3. Customize Nodes:
    • Chat Trigger: Configure how the chat messages are received (e.g., webhook, specific chat platform).
    • AI Agent: Adjust the prompt and tools for the AI Agent to generate content according to your specific needs.
    • Structured Output Parser: Define the schema for the expected output from the AI Agent.
    • Edit Fields: Customize the fields you want to process and transform.
    • If Node: Define the conditions for approval (e.g., based on content length, keywords, or a specific field from the AI output).
    • Slack & Gmail Nodes: Customize the messages and recipients for approval requests.
    • Google Sheets Node: Specify the spreadsheet ID, sheet name, and how the data should be written (e.g., append row, update row).
  4. Activate the Workflow: Once configured, activate the workflow to start automating your content publishing.

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

Wessel BulteBy Wessel Bulte
247

🎓 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.

DavideBy Davide
1616

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113