HumationHuman + Automation
Back to Catalog

Daily competitor WordPress analysis with charts, Gemini & Telegram reporting

Cong NguyenCong Nguyen
57 views
2/3/2026
Lead GenerationWebhookHubSpotSalesforceCRM
Official Page

What this workflow does

Every night at 22:00 (Asia/Ho_Chi_Minh), the workflow fetches the latest posts from multiple competitor WordPress RSS feeds, upserts them into Google Sheets, captures a dashboard screenshot (via ApiFlash), has Gemini Vision analyze the chart, and sends a concise insight report to Telegram.

Details

  • Schedule (22:00) → runs daily.
  • Fetch RSS → HTTP Request (or RSS Read) pulls each competitor’s /feed/ (standard WordPress RSS).
  • Normalize & limit → parse XML → JSON, keep the most recent 5 per site for the digest (you can raise/lower this).
  • Upsert to Google Sheets → match on link to avoid duplicates; store fields like guid, site, link, title, excerpt/description, content (if available), pubDate, updated.
  • Screenshot the dashboard → ApiFlash captures the Google Sheets dashboard (specific gid) with your line chart of monthly post counts.
  • Vision analysis → Gemini 1.5-Flash analyzes the chart image and returns a short executive summary, a Markdown table of values (≈ when estimated), insights, and recommended next steps.
  • Telegram push → posts the AI summary (and optionally the screenshot) to your channel/group.

Who it’s for

  • SEO/Content/Marketing teams tracking competitor publishing cadence.
  • Founders/PMs who want a nightly snapshot.
  • Competitive intelligence and analytics roles.

Requirements

  1. n8n (cloud or self-hosted).
  2. Google Sheets OAuth2, Telegram Bot, ApiFlash (access key), Google Gemini access.
  3. A Google Sheet with columns similar to: id/guid, site, link, title, excerpt, content, pubDate, updated.
  4. Setup
  5. Import the workflow JSON into n8n.
  6. Switch to RSS:
  • Option A (simple): replace HTTP nodes with RSS Read and paste each competitor’s https://{domain}/feed/.
  • Option B (keep HTTP): keep HTTP Request nodes, set Response: XML, then parse with XML node.
  1. Mapping to Sheets: point to your documentId and sheetName; set matching column = link for upsert.
  2. ApiFlash: add access_key and the Sheet URL with the correct gid that shows your chart; set scale_factor=2 (or higher for clarity).
  3. Gemini Vision: use model gemini-1.5-flash-latest with the included prompt (English output; Markdown table + insights + recommendations).
  4. Telegram: set bot credentials and chatId.
  5. Schedule: confirm 22:00 Asia/Ho_Chi_Minh (adjust as needed).
  6. Test: run once → verify rows append/update → see dashboard render → receive AI summary in Telegram.

Extending to more competitors

  • Clone an HTTP/RSS node for each additional competitor, update the /feed/ URL, and connect it to the Merge node.
  • No other changes are required—new data will be normalized, upserted, included in charts and in the AI summary automatically.
  • Tips & gotchas
  • WordPress RSS typically includes title, link, pubDate, guid, description, and sometimes content:encoded. If content:encoded is absent, fall back to description.
  • Keep the Sheet chart source range dynamic (e.g., open-ended ranges) so new rows are reflected automatically.
  • If a site’s RSS limits items, you can run multiple feeds (e.g., category feeds) or capture more history on the first run.

💡 About Margin AI

Margin Ai is an AI-services agency that acts as your AI Service Companion. We design intelligent, human-centric automation solutions—turning your team’s best practices into scalable workflows and tools. Industries like marketing, sales, and operations benefit from our tailored AI consulting, automation tools, and chatbot development.

Daily Competitor WordPress Analysis with Charts & Gemini + Telegram Reporting

This n8n workflow automates the daily analysis of competitor WordPress websites, generates insights using Google Gemini, and reports the findings to a Telegram chat. It's designed to keep you informed about key changes and trends in your competitive landscape without manual effort.

What it does

This workflow performs the following steps:

  1. Triggers Daily: The workflow is scheduled to run once every day.
  2. Fetches Competitor Data: It retrieves a list of competitor WordPress websites from a Google Sheet.
  3. Scrapes Website Data: For each competitor website, it makes an HTTP request to gather website information.
  4. Generates AI Analysis: It sends the scraped website data to Google Gemini to generate insights, identify changes, or summarize content.
  5. Aggregates Results: It combines the original website data with the AI-generated analysis.
  6. Limits Output: It ensures that only a manageable number of results are processed further.
  7. Sends Telegram Report: It compiles a summary of the analysis and sends it as a message to a specified Telegram chat.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: A Google Sheets spreadsheet containing a list of competitor WordPress website URLs.
    • You'll need to configure a Google Sheets credential in n8n.
  • Google Gemini API Key: Access to the Google Gemini API for AI analysis.
    • You'll need to configure a Google Gemini credential in n8n.
  • Telegram Account & Bot: A Telegram bot and chat ID to receive reports.
    • You'll need to configure a Telegram credential in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" -> "Import from JSON" and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Google Sheets: Open the "Google Sheets" node (ID: 18) and configure your Google Sheets credential. Ensure the spreadsheet ID and range are correctly set to fetch your competitor URLs.
    • Google Gemini: Open the "Google Gemini" node (ID: 1309) and configure your Google Gemini API key credential.
    • Telegram: Open the "Telegram" node (ID: 49) and configure your Telegram Bot API Token and Chat ID.
  3. Customize HTTP Request:
    • Open the "HTTP Request" node (ID: 19). You may need to adjust the URL expression to dynamically fetch the correct competitor URLs from your Google Sheet data.
  4. Customize Google Gemini Prompt:
    • Open the "Google Gemini" node (ID: 1309). Adjust the prompt to guide Gemini on what kind of analysis or insights you want to extract from the competitor website data.
  5. Customize Telegram Message:
    • Open the "Telegram" node (ID: 49). Adjust the message content to format the report as desired, using data from previous nodes (e.g., competitor name, website URL, Gemini analysis).
  6. Activate the Workflow:
    • Enable the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
  7. Adjust Schedule (Optional):
    • The "Schedule Trigger" node (ID: 839) is set to run daily. You can modify this schedule if needed (e.g., hourly, weekly).

Once activated, the workflow will run according to its schedule, providing you with automated competitor analysis reports directly in Telegram.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

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