This workflow automatically monitors blog posts or product pages for new/updated content, analyzes Google AI Overviews to identify optimization gaps, auto-generates optimized titles, summaries, and schema markup, and applies these improvements to enhance visibility in AI search results. Who's it for • SEO managers optimizing for AI-driven search results • Content teams publishing 5+ articles per week • E-commerce teams managing product page visibility • Digital marketers tracking AI Overview presence How it works / What it does Detects new or updated blog posts / product pages via webhook or schedule Fetches raw content and existing metadata Queries Google Search API to analyze AI Overview coverage gaps AI generates optimized title, meta summary, and JSON-LD schema markup Pushes improvements back to CMS or target endpoint Logs all changes and scores to Google Sheet tracker How to set up Import this workflow Set up credentials (Google Search API, OpenAI/Anthropic, CMS/HTTP, Google Sheets) Update your site URL and content preferences Activate workflow Requirements • Webhook endpoint or CMS trigger • Google Custom Search API key • OpenAI / Anthropic / Grok API • CMS REST API or target
Tags
OpenAI Chat ModelRelated workflows
See all AI Automation→
AI: Summarize podcast episode and enhance using Wikipedia
The workflow automates the process of creating a summarized and enriched podcast digest, which is then sent via email. Note that to use this template, you need to be on n8n version 1.19.4 or later.
Answer Slack knowledge base questions with Notion, Pinecone, and OpenAI
Quick overview This workflow syncs an internal Notion knowledge base to Pinecone on a daily schedule, then runs a Slack bot that answers questions in a specific channel using Pinecone retrieval and an OpenAI chat model, replying in a thread with citations back to the source Notion pages. How it works Runs on a daily schedule to sync your Notion knowledge base into a Pinecone vector index. Fetches all pages from a specified Notion database and then pulls each page’s full block content (including nested blocks). Combines each page’s blocks into a single document and attaches metadata such as the Notion title, URL, and last edited time. Splits each document into overlapping text chunks, generates OpenAI embeddings, and inserts them into Pinecone while clearing and rebuilding the target namespace. Triggers when a new message is posted in the configured Slack channel and ignores bot/system messages to prevent reply loops. Uses an OpenAI-powered agent that always queries Pinecone for relevant chunks (including source metadata) and generates an answer in the user’s language. Posts the response back to Slack as a threaded reply, including cited Notion sources. Setup Create a Notion interna
CWReport workflow errors to Asana tasks with Google Chat and Grok 4.5 analysis
Quick overview When a monitored workflow fails, this reads its Description field to find the owning client and assignee, looks them up in Asana, analyses the error with Grok 4.5, and creates an assigned task with a severity-based due date. Repeat failures comment on the existing task. How it works Any workflow that names this one as its error workflow triggers it on failure. There is no production trigger by design. The error payload only carries a workflow ID, so an HTTP Request calls the n8n API to read that workflow's own Description field, which holds a small JSON object naming the client and the assignee. Asana projects and users are fetched live and matched by name, so no GID is ever hardcoded. A failed match raises a warning that travels downstream instead of failing silently. Asana is searched for an open task covering the same workflow and node. If one exists, a comment carrying the new execution ID is added rather than a duplicate task. For a new error, Grok 4.5 via OpenRouter returns a root cause, a solution, concrete steps, a severity, and a category, held to a fixed shape by a structured output parser. Severity sets the due date: Critical today, High tomorrow, Medium i