Back to Catalog

Monitor regulatory updates with ScrapeGraphAI and send alerts via Telegram

vinci-king-01vinci-king-01
7 views
2/3/2026
Official Page

Breaking News Aggregator with Telegram and Redis

⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template.

This workflow monitors selected government websites, regulatory bodies, and legal-news portals for new or amended regulations relevant to specific industries. It scrapes the latest headlines, compares them against previously recorded items in Redis, and pushes real-time compliance alerts to a Telegram channel or chat.

Pre-conditions/Requirements

Prerequisites

  • n8n instance (self-hosted or cloud)
  • ScrapeGraphAI community node installed
  • Redis server accessible from n8n
  • Telegram Bot created via BotFather
  • (Optional) Cron node if you want fully automated scheduling instead of manual trigger

Required Credentials

  • ScrapeGraphAI API Key – Enables ScrapeGraphAI scraping functionality
  • Telegram Bot Token – Allows n8n to send messages via your bot
  • Redis Credentials – Host, port, and (if set) password for your Redis instance

Redis Setup Requirements

| Key Name | Description | Example | |----------|-------------|---------| | latestRegIds | Redis Set used to store hashes/IDs of the most recent regulatory articles processed | latestRegIds |

> Hint: Use a dedicated Redis DB (e.g., DB 1) to keep workflow data isolated from other applications.

How it works

This workflow monitors selected government websites, regulatory bodies, and legal-news portals for new or amended regulations relevant to specific industries. It scrapes the latest headlines, compares them against previously recorded items in Redis, and pushes real-time compliance alerts to a Telegram channel or chat.

Key Steps:

  • Manual Trigger / Cron: Starts the workflow manually or on a set schedule (e.g., daily at 06:00 UTC).
  • Code (Define Sources): Returns an array of URL objects pointing to regulatory pages to monitor.
  • SplitInBatches: Iterates through each source URL in manageable chunks.
  • ScrapeGraphAI: Extracts article titles, publication dates, and article URLs from each page.
  • Merge (Combine Results): Consolidates scraped items into a single stream.
  • If (Deduplication Check): Verifies whether each article ID already exists in Redis.
  • Set (Format Message): Creates a human-readable Telegram message string.
  • Telegram: Sends the formatted compliance alert to your chosen chat/channel.
  • Redis (Add New IDs): Stores the article ID so it is not sent again in the future.
  • Sticky Note: Provides inline documentation inside the workflow canvas.

Set up steps

Setup Time: 10-15 minutes

  1. Install community nodes: In n8n, go to Settings → Community Nodes and install n8n-nodes-scrapegraphai.
  2. Create credentials:
    a. Telegram → Credentials → Telegram API → paste your bot token.
    b. Redis → Credentials → Redis → fill host, port, password, DB.
    c. ScrapeGraphAI → Credentials → ScrapeGraphAI API → enter your key.
  3. Configure the “Define Sources” Code node: Replace the placeholder URLs with the regulatory pages you need to monitor.
  4. Update Telegram chat ID: Open any chat with your bot and use https://api.telegram.org/bot<token>/getUpdates to find the chat.id. Insert this value in the Telegram node.
  5. Adjust frequency: Replace the Manual Trigger with a Cron node (e.g., daily 06:00 UTC).
  6. Test the workflow: Execute once manually; confirm messages appear in Telegram and that Redis keys are created.
  7. Activate: Enable the workflow so it runs automatically according to your schedule.

Node Descriptions

Core Workflow Nodes:

  • Manual Trigger – Allows on-demand execution during development/testing.
  • Code (Define Sources) – Returns an array of page URLs and meta info to the workflow.
  • SplitInBatches – Prevents overloading websites by scraping in controlled groups.
  • ScrapeGraphAI – Performs the actual web scraping using an AI-assisted parser.
  • Merge – Merges data streams from multiple batches into one.
  • If (Check Redis) – Filters out already-processed articles using Redis SET membership.
  • Set – Shapes output into a user-friendly Telegram message.
  • Telegram – Delivers compliance alerts to stakeholders in real time.
  • Redis – Persists article IDs to avoid duplicate notifications.
  • Sticky Note – Contains usage tips directly on the canvas.

Data Flow:

  1. Manual TriggerCode (Define Sources)SplitInBatchesScrapeGraphAI
  2. ScrapeGraphAIMergeIf (Check Redis)
  3. If (true)SetTelegramRedis

Customization Examples

Change industries or keywords

// Code node snippet
return [
  {
    url: "https://regulator.gov/energy-updates",
    industry: "Energy",
    keywords: ["renewable", "grid", "tariff"]
  },
  {
    url: "https://financewatch.gov/financial-rules",
    industry: "Finance",
    keywords: ["AML", "KYC", "cryptocurrency"]
  }
];

Modify Telegram message formatting

// Set node “Parameters → Value”
items[0].json.message = `🛡️ *${$json.industry} Regulation Update*\n\n*${$json.title}*\n${$json.date}\n${$json.url}`;
return items;

Data Output Format

The workflow outputs structured JSON data:

{
  "title": "EU Proposes New ESG Disclosure Rules",
  "date": "2024-04-18",
  "url": "https://europa.eu/legal/eu-proposes-esg-disclosure",
  "industry": "Finance"
}

Troubleshooting

Common Issues

  1. Empty scraped data – Verify CSS selectors/XPath in the ScrapeGraphAI node; website structure may have changed.
  2. Duplicate alerts – Ensure Redis credentials point to the same DB across nodes; otherwise IDs are not shared.

Performance Tips

  • Limit SplitInBatches to 2-3 URLs at a time if sites implement rate limiting.
  • Use environment variables for credentials to simplify migration between stages.

Pro Tips:

  • Combine this workflow with n8n’s Error Trigger to log failures to Slack or email.
  • Maintain a CSV of source URLs in Google Sheets and fetch it dynamically via the Google Sheets node.
  • Pair with the Webhook node to let team members add new sources on the fly.

Monitor Regulatory Updates with ScrapeGraphAI and Send Alerts via Telegram

This n8n workflow provides a basic framework for processing data, potentially from a scraping operation (implied by the directory name "scrapegraphai"), and then sending alerts via Telegram based on certain conditions. It demonstrates how to use core n8n nodes for conditional logic, data manipulation, and notifications.

What it does

This workflow outlines the following steps:

  1. Manual Trigger: The workflow is initiated manually by clicking 'Execute workflow'.
  2. Conditional Logic: It includes an 'If' node, allowing for branching logic based on data received. This is where you would define conditions to filter or route information.
  3. Data Transformation: An 'Edit Fields (Set)' node is present, indicating that data fields can be modified or added.
  4. Looping/Batch Processing: A 'Loop Over Items (Split in Batches)' node suggests that the workflow is designed to process multiple items or records, potentially iterating over a list of scraped data.
  5. Data Storage/Retrieval (Placeholder): A 'Redis' node is included, which could be used for temporary storage, caching, or checking for previously processed items to avoid duplicate alerts.
  6. Data Merging: A 'Merge' node is available to combine data streams, possibly after conditional processing or looping.
  7. Custom Code Execution: A 'Code' node allows for custom JavaScript logic to be executed, offering flexibility for complex data manipulation or API interactions.
  8. Telegram Notification: A 'Telegram' node is configured to send messages, which would be used to deliver alerts or summaries.
  9. Documentation Note: A 'Sticky Note' is included for adding explanatory comments within the workflow.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • Telegram Bot Token and Chat ID: To send notifications via Telegram, you will need a Telegram bot token and the chat ID where messages should be sent. These will be configured in the Telegram node's credentials.
  • Redis Instance (Optional): If the Redis node is to be actively used, access to a Redis server will be required.
  • Data Source (External): While not explicitly defined in the JSON, the workflow's name implies an external data source, likely from a scraping tool like ScrapeGraphAI, which would feed data into this workflow.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Telegram: Set up your Telegram Bot API credentials in the 'Telegram' node.
    • Redis (if used): Configure your Redis connection details in the 'Redis' node if you intend to use it.
  3. Define Logic:
    • If Node: Customize the conditions in the 'If' node to match your specific alerting criteria (e.g., if a certain keyword is found, if a value exceeds a threshold).
    • Edit Fields (Set) Node: Adjust the fields to be set or modified based on your data processing needs.
    • Code Node: Implement any custom JavaScript logic required for advanced data manipulation or integration.
  4. Connect Data Source: Integrate this workflow with your data source (e.g., a webhook from ScrapeGraphAI, a scheduled HTTP request to an API, or a direct data input) to feed the relevant regulatory updates into the 'If' node.
  5. Activate the Workflow: Once configured, activate the workflow to enable it to run. For testing, you can use the 'Manual Trigger' node.

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 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

Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
110