Automated SEO content engine with Claude AI, Scrapeless, and competitor analysis
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it works This n8n workflow helps you build a fully automated SEO content engine using Scrapeless and AI. It’s designed for teams running international websites—such as SaaS products, e-commerce platforms, or content-driven businesses—who want to grow targeted search traffic through high-conversion content, without relying on manual research or hit-or-miss topics. The flow runs in three key phases: 🔍 Phase 1: Topic Discovery Automatically find high-potential long-tail keywords based on a seed keyword using Google Trends via Scrapeless. Each keyword is analyzed for trend strength and categorized by priority (P0–P3) with the help of an AI agent. 🧠 Phase 2: Competitor Research For each P0–P2 keyword, the flow performs a Google Search (via Deep SerpAPI) and extracts the top 3 organic results. Scrapeless then crawls each result to extract full article content in clean Markdown. This gives you a structured, comparable view of how competitors are writing about each topic. ✍️ Phase 3: AI Article Generation Using AI (OpenAI or other LLM), the workflow generates a complete SEO article draft, including: SEO title Slug Meta description Trend-based strategy summary Structured JSON-based article body with H2/H3 blocks Finally, the article is stored in Supabase (or any other supported DB), making it ready for review, API-based publishing, or further automation. Set up steps This flow requires intermediate familiarity with n8n and API key setup. Full configuration may take 30–60 minutes. ✅ Prerequisites Scrapeless account (for Google Trends and web crawling) LLM provider (e.g. OpenAI or Claude) Supabase or Google Sheets (to store keywords & article output) 🧩 Required Credentials in n8n Scrapeless API Key OpenAI (or other LLM) credentials Supabase or Google Sheets credentials --- 🔧 Setup Instructions (Simplified) Input Seed Keyword Edit the “Set Seed Keyword” node to define your niche, e.g., "project management". Google Trends via Scrapeless Use Scrapeless to retrieve “related queries” and their interest-over-time data. Trend Analysis with AI Agent AI evaluates each keyword's trend strength and assigns a priority (P0–P3). Filter & Store Keyword Data Group and sort keywords by priority, then store them in Google Sheets. Competitor Research Use Deep SerpAPI to get top 3 Google results. Crawl each using Scrapeless. AI Content Generation Feed competitor content + trend data into AI. Output a structured SEO blog article. Store Final Article Save full article JSON (title, meta, slug, content) to Supabase.
By scrapeless officialAutomated WhatsApp group weekly team reports with Gemini AI summarization
This n8n template automatically summarizes your WhatsApp group activity from the past week and generates a team report. Why use this? Remote teams rely on chat for communication, but important discussions, decisions, and ideas get buried in message threads and forgotten by Monday. This workflow ensures nothing falls through the cracks. How it works Runs every Monday at 6am to collect the previous week's group messages Groups conversations by participant and analyzes message threads AI summarizes individual member activity into personal reports Combines all individual reports into one comprehensive team overview Posts the final report back to your WhatsApp group to kick off the new week Setup requirements WhatsApp (whapAround.pro) no need Meta API Gemini AI (or alternative LLM of choice) Best practices Use one workflow per WhatsApp group for focused results Filter for specific team members if needed Customize the report tone to match your team culture Adjust the schedule if weekly reports don't suit your team's pace Customization ideas Send reports via email instead of posting to busy groups Include project metrics alongside message summaries Connect to knowledge bases or ticket systems for additional context Perfect for project managers who want to keep distributed teams aligned and ensure important conversations don't get lost in the chat noise.
By JamotMonitor security logs for failed login attempts with Slack alerts
How It Works: The 5-Node Anomaly Detection Flow This workflow efficiently processes logs to detect anomalies. Scheduled Check (Cron Node): This is the primary trigger. It schedules the workflow to run at a defined interval (e.g., every 15 minutes), ensuring logs are routinely scanned for suspicious activity. Fetch Logs (HTTP Request Node): This node is responsible for retrieving logs from an external source. It sends a request to your log API endpoint to get a batch of the most recent logs. Count Failed Logins (Code Node): This is the core of the detection logic. The JavaScript code filters the logs for a specific event ("login_failure"), counts the total, and identifies unique IPs involved. This information is then passed to the next node. Failed Logins > Threshold? (If Node): This node serves as the final filter. It checks if the number of failed logins exceeds a threshold you set (e.g., more than 5 attempts). If it does, the workflow is routed to the notification node; if not, the workflow ends safely. Send Anomaly Alert (Slack Node): This node sends an alert to your team if an anomaly is detected. The Slack message includes a summary of the anomaly, such as the number of failed attempts and the IPs involved, enabling a swift response. --- How to Set Up Implementing this essential log anomaly detector in your n8n instance is quick and straightforward. Prepare Your Credentials & API: Log API: Make sure you have an API endpoint or a way to get logs from your system (e.g., a server, CMS, or application). The logs should be in JSON format, and you'll need any necessary API keys or tokens. Slack Credential: Set up a Slack credential in n8n and get the Channel ID of your security alert channel (e.g., security-alerts). Import the Workflow JSON: Create a new workflow in n8n and choose "Import from JSON." Paste the JSON code (which was provided in a previous response). Configure the Nodes: Scheduled Check (Cron): Set the schedule according to your preference (e.g., every 15 minutes). Fetch Logs (HTTP Request): Update the URL and header/authentication to match your specific log API endpoint. Count Failed Logins (Code): Verify that the JavaScript code matches your log's JSON format. You may need to adjust log.event === 'login_failure' if your log events use a different name. Failed Logins > Threshold? (If): Adjust the threshold value (e.g., 5) based on your risk tolerance. Send Anomaly Alert (Slack): Select your Slack credential and enter the correct Channel ID. Test and Activate: Manual Test: Run the workflow manually to confirm it fetches logs and processes them correctly. You can temporarily lower the threshold to 0 to ensure the alert is triggered. Verify Output: Check your Slack channel to confirm that alerts are formatted and sent correctly. Activate: Once you're confident in its function, activate the workflow. n8n will now automatically monitor your logs on the schedule you set.
By MarthSubmit iOS meeting notes to Obsidian using local AI transcription
This workflow enables seamless, privacy-first capture of meeting notes from your iPhone. It pairs with an iOS Shortcut that leverages Apple’s on-device transcription from the Voice Memos app and optionally passes the output to ChatGPT or a local AI model for summarization. Who it's for Anyone who wants fast, secure note capture on iOS Professionals (e.g., lawyers, therapists) who require on-device processing for privacy Obsidian users who want to sync mobile notes via Google Drive What it does You record a voice memo in the iOS Voice Memos app. The Shortcut transcribes it locally (no API or cloud involved). Optionally, a summarization step is done via ChatGPT or a replaceable local model. The data is sent to an n8n webhook, where it’s converted into a .md file. The Markdown file is uploaded to a Google Drive folder synced with your Obsidian vault. Key Benefits 🧠 Keeps your meeting notes private — no cloud APIs required 🗃️ Easily searchable in Obsidian as structured Markdown files 🛠️ Fully local if you swap out ChatGPT for a local model (can be less stable) Limitations Transcriptions longer than ~1 hour may fail or produce unstable results. Some setup required to replace ChatGPT with a local model in the Shortcut. Setup Install and configure the iOS Shortcut Replace the ChatGPT step in the Shortcut if you need full local-only processing Point the webhook in the Shortcut to your n8n instance Make sure your Obsidian vault is synced with the Google Drive folder used in the workflow Update any of the prompts in the iOS shortcut to ensure its personalized. > ⚡ Pro Tip: Use a Set node early on to clearly define the filename, title, and text so it's easier to modify this for other note types (e.g., journals, therapy sessions, etc.)
By Angel MenendezSync upcoming anime releases from Jikan API to Google Calendar with rate limiting
Who is this for Anime Enthusiasts: Users who want to automate their watchlists based on specific voice actors or creators. n8n Learners: Anyone looking for a best-practice example of handling API rate limiting, loops, and data filtering. Calendar Power Users: People who want to populate their personal schedule with external data sources automatically. What it does Search: Queries the Jikan API for a specific person (e.g., Voice Actor "Mamoru Miyano"). Wait: Pauses execution to respect the API rate limit. Retrieve: Fetches the list of anime roles associated with that person. Loop & Filter: Iterates through the list one by one, fetches detailed status, and filters for shows marked as "Not yet aired." Schedule: Creates an event in your Google Calendar using the anime's title and release date. Setup Steps Configure Search: Open the 'Search Voice Actor' node. In "Query Parameters," change the value of q to the name of the voice actor or person you want to track. Connect Calendar: Open the 'Create an event' node. Select your Google Calendar credentials and choose the Calendar ID where events should be created. Test: Run the workflow manually to populate your calendar. Requirements An active n8n instance. A Google account (for Google Calendar). No API Key is required for Jikan API (Public), but rate limiting logic must be preserved. How to customize Change the Filter: Modify the 'Check if Not Aired' node to track "Currently Airing" shows instead of upcoming ones. Enrich Event Details: Update the 'Create an event' node to include the MyAnimeList URL or synopsis in the calendar event description. Search Different Entities: Adjust the API endpoint to search for Manga authors or specific Studios instead of voice actors. Expected Result Upon successful execution, this workflow will: Search for the specified voice actor. Retrieve their upcoming anime roles. Create events in your Google Calendar for anime that hasn't aired yet. Example Calendar Entry: Title: Anime Name - Release Date Description: Details regarding the release...
By Miki AraiAI-powered n8n release notes summary notifications via Gmail with GPT-5-Mini
Who's it for This workflow is perfect for n8n users and teams who want to stay up-to-date with the latest n8n releases without manually checking GitHub. Get AI-powered summaries of new features and bug fixes delivered straight to your inbox. What it does This workflow automatically monitors the n8n GitHub releases page and sends you smart email notifications when new updates are published. It fetches release notes, filters them based on your schedule (daily, weekly, etc.), and uses OpenAI to generate concise summaries highlighting the most important bug fixes and features. The summaries are then formatted into a clean HTML email and sent via Gmail. How to set up Configure the Schedule Trigger - Set how often you want to check for updates (daily, weekly, etc.) Add OpenAI credentials - Connect your OpenAI API key or use a different LLM Add Gmail credentials - Connect your Google account Set recipient email - Update the "To" email address in the Gmail node Activate the workflow and you're done! Requirements OpenAI API account (or alternative LLM) Gmail account with n8n credentials configured How to customize Adjust the schedule trigger to match your preferred notification frequency The filtering logic automatically adapts to your schedule (24 hours for daily, 7 days for weekly, etc.) Modify the AI prompt to focus on different aspects of the release notes Customize the HTML email template to match your preferences
By Jeff Huera