Back to Catalog

Daily AI news monitoring and summarization with GPT-4 from Google & Hacker News to Telegram

ManoMano
1225 views
2/3/2026
Official Page

📰 What This Workflow Does

This intelligent news monitoring system automatically:

RSS Feed Aggregation: Pulls the latest headlines from Google News RSS feeds and Hacker News • AI Content Filtering: Identifies and prioritizes AI-related news from the past 24 hours • Smart Summarization: Uses OpenAI to create concise, informative summaries of top stories • Telegram Delivery: Sends formatted news digests directly to your Telegram channel • Scheduled Execution: Runs automatically every morning at 8:00 AM (configurable)

🎯 Key Features

Multi-Source News: Combines Google News and Hacker News for comprehensive coverage ✅ AI-Powered Filtering: Automatically identifies relevant AI and technology news ✅ Intelligent Summarization: OpenAI generates clear, concise summaries with key insights ✅ Telegram Integration: Instant delivery to your preferred chat or channel ✅ Daily Automation: Scheduled to run every morning for fresh news updates ✅ Customizable Timing: Easy to adjust schedule for different time zones

🔧 How It Works

  1. Scheduled Trigger: Workflow activates daily at 8:00 AM (or your preferred time)
  2. RSS Feed Reading: Fetches latest articles from Google News and Hacker News feeds
  3. Content Filtering: Identifies AI-related stories from the past 24 hours
  4. AI Summarization: OpenAI processes and summarizes the most important stories
  5. Telegram Delivery: Sends formatted news digest to your Telegram channel

📋 Setup Requirements

OpenAI API Key: For AI-powered news summarization • Telegram Bot: Create via @BotFather and get bot token + chat ID • RSS Feed Access: Google News and Hacker News RSS feeds (public)

⚙️ Configuration Steps

  1. Set Up Telegram Bot:

    • Message @BotFather on Telegram
    • Create new bot with /newbot command
    • Save bot token and chat ID
  2. Configure OpenAI:

    • Add OpenAI API credentials in n8n
    • Ensure access to GPT models for summarization
  3. Update RSS Feeds:

    • Verify Google News RSS feed URLs
    • Confirm Hacker News feed accessibility
  4. Schedule Timing:

    • Adjust Schedule Trigger for your time zone
    • Default: 8:00 AM daily (modify as needed)
  5. Test & Deploy:

    • Run test execution to verify all connections
    • Activate workflow for daily automation

🎨 Customization Options

Time Zone Adjustment: Modify Schedule Trigger for different regions News Sources: Add additional RSS feeds for broader coverage Filtering Criteria: Adjust AI prompts to focus on specific topics Summary Length: Customize OpenAI prompts for different detail levels Delivery Format: Modify Telegram message formatting and structure

💡 Use Cases

AI Professionals: Stay updated on latest AI developments and industry news • Tech Teams: Monitor technology trends and competitor announcements • Researchers: Track academic and industry research developments • Content Creators: Source material for AI-focused content and newsletters • Business Leaders: Stay informed about AI market trends and opportunities

Daily AI News Monitoring and Summarization with GPT-4 from Google & Hacker News to Telegram

This n8n workflow automates the process of monitoring RSS feeds for AI-related news, summarizing the articles using an OpenAI GPT model, and then posting these summaries to a Telegram channel. It's designed to keep you updated on the latest AI developments without manually sifting through numerous articles.

What it does

  1. Schedules Execution: The workflow runs on a predefined schedule (e.g., daily) to check for new articles.
  2. Reads RSS Feeds: It fetches the latest articles from specified RSS feeds (e.g., n8n blog posts in the provided JSON).
  3. Limits Articles: It can be configured to process only a certain number of the most recent articles from the feed.
  4. Summarizes with AI: For each article, it uses an OpenAI Chat Model (like GPT-4) to generate a concise summary.
  5. Posts to Telegram: The generated summary is then sent as a message to a specified Telegram chat or channel.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Telegram Bot Token: A Telegram bot token and the chat ID of the channel/group where you want to post the summaries.
  • OpenAI API Key: An API key for OpenAI to access their chat models (e.g., GPT-4).
  • RSS Feed URLs: The URLs of the RSS feeds you wish to monitor for AI news.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the copied JSON.
  2. Configure Credentials:
    • Telegram:
      • Locate the "Telegram" node.
      • Click on the "Credential" field and select "Create New Credential".
      • Choose "Telegram API" and enter your Telegram Bot Token.
      • In the "Chat ID" field of the Telegram node, enter the ID of your target Telegram chat or channel.
    • OpenAI Chat Model:
      • Locate the "OpenAI Chat Model" node.
      • Click on the "Credential" field and select "Create New Credential".
      • Choose "OpenAI API" and enter your OpenAI API Key.
  3. Configure RSS Feeds:
    • Locate the "RSS Read" node.
    • In the "URL" field, replace the example n8n blog URLs with the RSS feed URLs relevant to AI news that you want to monitor.
  4. Adjust Limit (Optional):
    • Locate the "Limit" node.
    • Adjust the "Amount" property if you want to limit the number of articles processed per run (e.g., to only summarize the top 3 latest articles).
  5. Customize AI Prompt (Optional):
    • Locate the "Basic LLM Chain" node.
    • Review the prompt being sent to the OpenAI model. You can modify it in the "Code" node (if present and generating the prompt) or directly within the "Basic LLM Chain" node's configuration to refine how summaries are generated.
  6. Activate the Workflow:
    • Ensure all nodes are correctly configured.
    • Click the "Activate" toggle in the top right corner of the n8n editor to enable the workflow.
    • The workflow will now run automatically based on the schedule defined in the "Schedule Trigger" node. You can also manually execute it by clicking "Execute Workflow".

This workflow provides a robust foundation for automated AI news monitoring. You can extend it further by adding more RSS feeds, integrating with other AI models, or even storing the summaries in a database.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942