Autonomous blog publishing from YouTube videos with ChatGPT, Sheets, Apify, Pexels & WordPress

124 views

2/3/2026

Conditional Logic Webhook Integration Data Processing HTTP Request

Autonomous YouTube - Blog Builder / SEO Autopublisher (Sheets, ChatGPT, Apify, Pexels, WordPress) – Multilanguage

100% autonomous workflow that transforms YouTube videos into unique, high-quality, SEO-optimized blog articles and automatically publishes them to WordPress. No human intervention required: it uses YouTube as the main source for fresh, original content ideas, manages a keyword bank in Google Sheets, finds relevant videos via Apify, transcribes, writes, formats, selects a featured image via Pexels, generates SEO metadata, and publishes. When all keywords are used, it will automatically generate new ones (avoiding duplicates) to keep producing content without interruptions.

Estimated cost per post (including ChatGPT + Apify (free 5$ new user)) → $0.01 – $0.03 depending on video length.

Includes:

Access to APIs with 7-day free trials (Apify, Pexels, etc.).
Step-by-step documentation to get each API key.
Basic setup support to get you started.

Who it’s for

Agencies and creators looking to scale blogging from video content.
SEO teams needing automation with quality control.
Technical bloggers who want hands-off publishing with tracking.

SEO

SEO teams needing automation with quality control (modifiable from the options node like including h1, hierarchy among other SEO options).
The title and description of the page (SEO) is based on the language in which the blog was created
Allows you to add keywords

How it works (phase summary)

Part 1 – Keyword initialization

Manual or scheduled trigger.
Checks if the Google Sheet is empty; if so, generates 10 keywords based on a seed idea and saves them.

Part 2 – Keyword management & blog settings

Includes an “options” node to configure global blog language and formatting rules (H1, headings, bold, intro, conclusion, etc.).
Selects a keyword with false status (unused), marks it true with a usage date, and if none are left, generates new ones while avoiding duplicates.

Part 3 – Video search & duplicate filtering

Searches YouTube via Apify using the keyword, retrieves ~30 results, excludes Shorts, and selects 2 videos based on title/description/hashtags.
Checks for duplicates; if found, retries up to 5 times with variations.
If still duplicated, discards the keyword and selects another.

Error Handling & Continuity

Includes fallbacks and failure alerts in every critical node to ensure the workflow keeps running even if a step fails.

Part 4 – Article creation

Transcribes the video (cost included in $0.01–$0.03).
ChatGPT writes a formal blog post in the language set in the “options” node.
A second ChatGPT step applies the formatting rules (structure, H1/H2…, intro/conclusion).
Ensures SEO compliance.
Converts Markdown → HTML and publishes to WordPress (more info results screenshots).

Part 5 – Image & final publishing

Searches Pexels API for images using the post keyword.
ChatGPT chooses the most suitable image; it’s downloaded and attached to the post.
Generates an SEO title and meta description based on the content.
Sends an email confirmation with the published URL (with the chosen language, more info screenshots).

Requirements

OpenAI / ChatGPT (or compatible provider for transcription and writing).
Google Sheets (keyword storage and usage tracking).
Apify (YouTube search (free 5$ new user)).
Pexels API (image sourcing (free api)).
WordPress REST API (user with permissions to create posts/media).

Costs & limits (important)

Cost per post: $0.01 – $0.03 (ChatGPT + Apify included (free 5$ new user)).
Rate limits: respect YouTube/Apify, Pexels, and OpenAI limits.

Thoroughly Tested for Reliability and Performance

This workflow has been carefully tested in multiple scenarios to ensure optimal functionality, stability, and accuracy.
Various edge cases and potential failure points were simulated, and fallback mechanisms were implemented to handle unexpected situations.
The result is a robust and reliable automation you can run confidently in production environments.

The workflow is multi-language and it has been tested to create blogs in (Russian, Spanish, English, German and French) all the results were verified and good

Screenshots

More info and photos: oriolrotllant3@gmail.com

# Autonomous Blog Publishing from YouTube Videos with AI and WordPress

This n8n workflow automates the entire process of generating and publishing blog posts on WordPress, using YouTube video content as the primary source. It leverages AI (via OpenAI and Langchain) to transcribe, summarize, and transform video content into engaging blog posts, and then publishes them, optionally notifying via Gmail.

## What it does

This workflow streamlines content creation by:

1.  **Triggering**: The workflow can be triggered manually or on a schedule.
2.  **Fetching YouTube Video Data**: It starts by retrieving information about a YouTube video from a Google Sheet.
3.  **Transcribing Video (via Apify/HTTP Request)**: It uses an HTTP Request node, likely connected to an Apify actor, to get the transcript of the specified YouTube video.
4.  **Generating Blog Content with AI**:
    *   **Summarizing Transcript**: The video transcript is summarized using an AI agent (Langchain with OpenAI Chat Model and Simple Memory).
    *   **Structuring Output**: A Structured Output Parser ensures the AI output is in a usable format for the blog post.
    *   **Generating Title and Content**: The AI agent generates a blog post title, content, and an excerpt based on the summarized transcript.
5.  **Processing and Formatting**:
    *   **Renaming Keys**: Data keys are renamed for consistency.
    *   **Setting Fields**: Additional fields are set, potentially for WordPress categories or tags.
    *   **Converting to Markdown**: The generated content is converted into Markdown format.
6.  **Conditional Publishing**:
    *   **Review Check**: An "If" node checks a condition (e.g., if a review is required or if the content is ready).
    *   **Publishing to WordPress**: If the review condition is met (or skipped), the blog post is published to WordPress.
    *   **Sending for Review (Optional)**: If a review is required, the content is sent via Gmail for human review.
7.  **Error Handling**: A "Stop and Error" node is included for handling unexpected issues.

## Prerequisites/Requirements

To use this workflow, you will need:

*   **n8n Instance**: A running instance of n8n.
*   **Google Sheets Account**: To store YouTube video URLs and metadata.
*   **OpenAI API Key**: For the AI Agent (Langchain with OpenAI Chat Model).
*   **WordPress Account**: With API access for publishing posts.
*   **Apify Account (or similar transcription service)**: The HTTP Request node is configured to call an external service (likely Apify) for YouTube video transcription. You'll need credentials and a configured actor/endpoint.
*   **Gmail Account**: For sending review emails (if the review process is enabled).

## Setup/Usage

1.  **Import the workflow**: Download the JSON file and import it into your n8n instance.
2.  **Configure Credentials**:
    *   **Google Sheets**: Set up your Google Sheets credential.
    *   **OpenAI**: Configure your OpenAI API key credential.
    *   **WordPress**: Set up your WordPress credential (API key or OAuth).
    *   **Gmail**: Configure your Gmail credential.
3.  **Configure Apify (or transcription service)**:
    *   In the "HTTP Request" node, update the URL and any necessary headers/body parameters to call your YouTube transcription service (e.g., an Apify actor).
4.  **Google Sheet Setup**:
    *   Create a Google Sheet with a column for YouTube video URLs (and any other relevant metadata you want to use).
    *   Update the "Google Sheets" node to point to your specific spreadsheet and sheet name.
5.  **Customize AI Prompts**:
    *   Review and adjust the prompts within the "AI Agent" nodes to fine-tune the blog post generation (e.g., tone, length, specific keywords).
6.  **Adjust "If" Node Logic**:
    *   Modify the conditions in the "If" node to control when posts are directly published or sent for review.
7.  **Activate the workflow**: Enable the workflow to run automatically on a schedule or trigger it manually.

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

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

By Davide

1616

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

By Oneclick AI Squad