Back to Catalog

Analyze crypto news sentiment for any token with GPT-4o and Telegram alerts

Don Jayamaha JrDon Jayamaha Jr
11240 views
2/3/2026
Official Page

A sentiment intelligence sub-agent for the Binance Spot Market Quant AI Agent. It aggregates crypto news from major sources, filters by token keyword (e.g., BTC, ETH), and produces a Telegram-ready summary including market sentiment and top headlines—powered by GPT-4o.

🎥 Live Demo: Click to Watch


🛠️ Workflow Function

This tool performs the following steps:

| 🔧 Step | 📌 Description | | ------------------------ | ----------------------------------------------------------------------------- | | Webhook Input | Accepts { "message": "symbol" } via HTTP POST | | Crypto Keyword Extractor | GPT model extracts the valid crypto symbol (e.g., "SOL", "DOGE", "ETH") | | RSS News Aggregators | Pulls latest headlines from 9+ crypto sources (CoinDesk, Cointelegraph, etc.) | | Merge & Filter Articles | Keeps only articles containing the specified token | | Prompt Builder | Creates prompt for GPT with filtered headlines | | GPT-4o Summarizer | Summarizes news into 3-part response: Summary, Sentiment, Headline Links | | Telegram Formatter | Converts GPT output into a Telegram-friendly message | | Response Handler | Returns formatted message to the caller via webhook |


📥 Webhook Trigger Format

{
  "message": "ETH"
}

This triggers a full execution of the workflow and returns output like:

📣 ETH Sentiment: Neutral

• BlackRock’s tokenized fund expands to Ethereum mainnet (CoinDesk)  
• Ethereum fees remain high, analysts call for L2 migration (NewsBTC)  
• Vitalik warns about centralized risks in staking (Cointelegraph)

📚 Installation Guide

1. Import & Enable

  • Load the .json into your n8n Editor
  • Enable webhook trigger in the top-right corner
  • Ensure it's reachable via POST /webhook/custom-path

2. Required Credentials

  • OpenAI API Key (GPT-4o capable)
  • No API keys required for RSS feeds

3. Connect to Quant Agent

  • Add an HTTP Request node in your main AI agent
  • Point to this workflow's webhook with body { "message": "symbol" }
  • Capture the response to include in your Telegram output

🔍 Real Use Cases

| Scenario | Result | | ---------------------------------- | ---------------------------------------------------------------- | | BTC Sentiment before a key event | Returns 8–12 filtered articles with bullish/neutral/bearish tone | | Daily pulse for altcoins like DOGE | Shows relevant headlines, helpful for intraday trading setups | | Telegram chatbot integration | Enables user to query sentiment via /sentiment ETH | | Macro context for Quant AI outputs | Adds emotional/news context to technical-based trade decisions |


🧾 Licensing & Attribution

© 2025 Treasurium Capital Limited Company Architecture, prompts, and trade report structure are IP-protected. No unauthorized rebranding or resale permitted.

🔗 For support: LinkedIn – Don Jayamaha

Analyze Crypto News Sentiment for Any Token with GPT-4o and Telegram Alerts

This n8n workflow automates the process of monitoring crypto news, analyzing the sentiment for a specified token using GPT-4o, and sending Telegram alerts for significant news. It allows you to stay informed about market-moving news for your chosen cryptocurrency without constant manual checking.

What it does

  1. Triggers on Demand: The workflow is manually triggered via a webhook, allowing you to initiate a news scan whenever needed.
  2. Fetches Crypto News: It reads the latest cryptocurrency news from an RSS feed (e.g., CoinDesk).
  3. Filters News for a Specific Token: It uses a Code node to filter the fetched news, keeping only articles that mention a user-defined crypto token (e.g., "Bitcoin", "Ethereum").
  4. Analyzes News Sentiment with GPT-4o: For each relevant news article, it leverages an OpenAI Chat Model (GPT-4o) to determine the sentiment (positive, negative, neutral) and extract a concise summary.
  5. Generates Sentiment-Based Alerts: It prepares a formatted message including the news title, summary, sentiment, and a direct link to the article.
  6. Sends Telegram Alerts: It sends these formatted alerts to a specified Telegram chat, ensuring you receive timely notifications.
  7. Responds to Webhook: After processing, it sends a confirmation back to the triggering webhook.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: An API key for OpenAI (specifically for GPT-4o access).
  • Telegram Bot Token: A Telegram bot token for sending messages.
  • Telegram Chat ID: The chat ID where the bot should send messages.
  • RSS Feed URL: A URL for a cryptocurrency news RSS feed (e.g., CoinDesk RSS).

Setup/Usage

  1. Import the Workflow:

    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots in the top right corner and select "Import from JSON".
    • Paste the JSON and click "Import".
  2. Configure Credentials:

    • OpenAI Chat Model (ID: 1153):
      • Click on the "OpenAI Chat Model" node.
      • Under "Credentials", select your existing OpenAI API credential or create a new one by providing your OpenAI API Key.
      • Ensure the "Model" is set to gpt-4o.
    • OpenAI (ID: 1250):
      • Click on the "OpenAI" node.
      • Under "Credentials", select your existing OpenAI API credential or create a new one by providing your OpenAI API Key.
      • Ensure the "Model" is set to gpt-4o.
    • Telegram (Not explicitly present in JSON, but implied by the workflow description):
      • If you intend to send Telegram alerts (as suggested by the directory name), you will need to add a Telegram node after the sentiment analysis.
      • Configure a Telegram node with your Telegram Bot Token and Chat ID. This node is not included in the provided JSON but would be a logical addition for the described functionality.
  3. Configure the RSS Feed:

    • Click on the "RSS Read" node (ID: 37).
    • Enter the URL of the cryptocurrency news RSS feed you wish to monitor (e.g., https://www.coindesk.com/feed/).
  4. Define the Crypto Token:

    • Click on the "Code" node (ID: 834).
    • Locate the code that defines the crypto token to analyze. You will need to modify this to specify the token you are interested in (e.g., "Bitcoin", "Ethereum", "Solana").
  5. Activate the Workflow:

    • Click the "Activate" toggle in the top right corner of the n8n editor.
  6. Trigger the Workflow:

    • The workflow is triggered by a "Webhook" node (ID: 47).
    • Copy the webhook URL from the "Webhook" node.
    • You can trigger this URL manually (e.g., by pasting it into your browser) or programmatically from another application or scheduler.
  7. Review Results:

    • After triggering, the workflow will fetch news, analyze sentiment, and (if a Telegram node is added) send alerts.
    • You can review the execution results in n8n to see the output of each node.

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