Chat with news articles using AI analysis in Telegram with vector search
π Overview
This workflow allows users to send any newspaper or article link to a Telegram bot. The workflow then:
- Validates the URL
- Scrapes the webpage (title, description, full text, images, OG metadata)
- Processes it using a Vision-Language Model (VLM)
- Generates structured summaries & highlights
- Downloads images (if available)
- Sends a formatted report + document back to Telegram
- Stores the summary in a vector database
- Allows users to chat with the article using semantic search
Perfect for: β News researchers β Students β Journalists β Telegram-based AI assistants β Automated media monitoring
π§ What the Workflow Does
1. Telegram Trigger
- Listens for messages from the user.
- Detects if the message contains a valid link.
2. URL Scraper
A custom n8n Code node fetches the webpage and extracts:
- Meta description paragraph text
- All image sources
- Open Graph metadata (og:title, og:image)
Returns everything as structured JSON.
3. VLM Run β Highlighter
A Vision-Language Model analyzes the scraped content and outputs:
{
"news_summary": {
"headline": "",
"source_url": "",
"published_date": "",
"key_points": "",
"summary": "",
"extracted_images_url": ""
}
}
4. Image Validation & Download
- Checks if image URLs are valid.
- Downloads them (if any).
- Sends them to Telegram as documents.
5. Summary File Generation
- Converts VLM output into a
.txtreport. - Sends the report back to the user.
6. Vector Store + Q&A Agent
-
Converts the summary into embeddings.
-
Stores the vector in an in-memory store.
-
Provides the user with a chat interface:
- Ask anything about the newspaper article.
- The AI agent retrieves information using the vector store.
π€ Outputs
You receive:
β Telegram message summary
β Downloadable summary .txt file
β Extracted images (if available)
β Chat-based Q&A agent to explore the newspaper details
π Use Cases
- News summarization bots
- Media intelligence agents
- Educational news explorers
- Topic-based daily digest creators
Chat with News Articles using AI Analysis in Telegram with Vector Search
This n8n workflow enables you to interact with news articles using AI-powered analysis and vector search, all within your Telegram chat. It allows you to ask questions about news content, receive AI-generated summaries, and find relevant articles based on your queries.
What it does
This workflow automates the following steps:
- Listens for Telegram Messages: It acts as a Telegram bot, waiting for incoming messages from users.
- Analyzes User Input: When a message is received, it determines if the message is a query for AI analysis or a command.
- Processes AI Queries:
- If the message is an AI query, it uses an OpenAI Chat Model to understand the user's request.
- It then generates embeddings for the query using OpenAI Embeddings.
- It performs a vector search against a "Simple Vector Store" (an in-memory vector store) to find relevant news articles.
- A "Default Data Loader" is used to process the retrieved documents.
- The AI Agent then synthesizes an answer based on the user's query and the retrieved article content.
- A "Structured Output Parser" helps format the AI's response.
- Responds via Telegram: The AI's answer or a predefined response is sent back to the user in Telegram.
- Handles Non-AI Messages: If the message is not an AI query, it passes through a "No Operation" node, effectively ignoring it or allowing for future expansion.
- Data Transformation: It uses "Edit Fields (Set)", "HTTP Request", "Convert to File", and "Split Out" nodes, likely for preparing or processing data related to news articles before they are stored in the vector database or for fetching news content.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Telegram Bot: A Telegram bot token (obtained from BotFather) configured as a credential in n8n.
- OpenAI API Key: An OpenAI API key configured as a credential in n8n for the Chat Model and Embeddings.
- News Article Data: While not explicitly defined in the provided JSON, a mechanism to feed news articles into the "Simple Vector Store" is implied. This would typically involve fetching articles (e.g., via HTTP Request), processing their content, generating embeddings, and storing them in the vector store. The current workflow focuses on the query and response part.
Setup/Usage
- Import the Workflow: Download the JSON and import it into your n8n instance.
- Configure Credentials:
- Telegram: Set up your Telegram Bot API credential.
- OpenAI: Set up your OpenAI API Key credential.
- Populate the Vector Store: This workflow assumes the "Simple Vector Store" is already populated with news article embeddings. You will need a separate process (or extend this workflow) to:
- Fetch news articles (e.g., using the "HTTP Request" node to an RSS feed or news API).
- Process the article content (e.g., using "Edit Fields" and "Default Data Loader").
- Generate embeddings for each article using the "Embeddings OpenAI" node.
- Add these embeddings and their associated text to the "Simple Vector Store".
- Activate the Workflow: Once all credentials are set and the vector store is populated, activate the workflow.
- Chat in Telegram: Send messages to your Telegram bot. The bot will analyze your queries using AI and respond with relevant information from the news articles.
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.
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
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