Back to Catalog

Analyze cryptocurrency market data with HTX API, GPT-4o and Telegram

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

A fully autonomous, HTX Spot Market AI Agent (Huobi AI Agent) built using GPT-4o and Telegram. This workflow is the primary interface, orchestrating all internal reasoning, trading logic, and output formatting.


โš™๏ธ Core Features

  • ๐Ÿง  LLM-Powered Intelligence: Built on GPT-4o with advanced reasoning
  • โฑ๏ธ Multi-Timeframe Support: 15m, 1h, 4h, and 1d indicator logic
  • ๐Ÿงฉ Self-Contained Multi-Agent Workflow: No external subflows required
  • ๐Ÿงฎ Real-Time HTX Market Data: Live spot price, volume, 24h stats, and order book
  • ๐Ÿ“ฒ Telegram Bot Integration: Interact via chat or schedule
  • ๐Ÿ”„ Autonomous Runs: Support for webhook, schedule, or Telegram triggers

๐Ÿ“ฅ Input Examples

| User Input | Agent Action | | --------------- | --------------------------------------------- | | btc | Returns 15m + 1h analysis for BTC | | eth 4h | Returns 4-hour swing data for ETH | | bnbusdt today | Full day snapshot with technicals + 24h stats |


๐Ÿ–ฅ๏ธ Telegram Output Sample

๐Ÿ“Š BTC/USDT Market Summary

๐Ÿ’ฐ Price: $62,400  
๐Ÿ“‰ 24h Stats: High $63,020 | Low $60,780 | Volume: 89,000 BTC

๐Ÿ“ˆ 1h Indicators:
โ€ข RSI: 68.1 โ†’ Overbought  
โ€ข MACD: Bearish crossover  
โ€ข BB: Tight squeeze forming  
โ€ข ADX: 26.5 โ†’ Strengthening trend

๐Ÿ“‰ Support: $60,200  
๐Ÿ“ˆ Resistance: $63,800

๐Ÿ› ๏ธ Setup Instructions

  1. Create your Telegram Bot using @BotFather

  2. Add Bot Token in n8n Telegram credentials

  3. Add your GPT-4o or OpenAI-compatible key under HTTP credentials in n8n

  4. (Optional) Add your HTX API credentials if expanding to authenticated endpoints

  5. Deploy this main workflow using:

    • โœ… Webhook (HTTP Request Trigger)
    • โœ… Telegram messages
    • โœ… Cron / Scheduled automation

๐ŸŽฅ Live Demo

Watch the Live Demo


๐Ÿง  Internal Architecture

| Component | Role | | ------------------ | -------------------------------------------------------- | | ๐Ÿ”„ Telegram Trigger | Entry point for external or manual signal | | ๐Ÿง  GPT-4o | Symbol + timeframe extraction + strategy generation | | ๐Ÿ“Š Data Collector | Internal tools fetch price, indicators, order book, etc. | | ๐Ÿงฎ Reasoning Layer | Merges everything into a trading signal summary | | ๐Ÿ’ฌ Telegram Output | Sends formatted HTML report via Telegram |


๐Ÿ“Œ Use Case Examples

| Scenario | Outcome | | -------------------------------------- | ------------------------------------------------------- | | Auto-run every 4 hours | Sends new HTX signal summary to Telegram | | Human requests โ€œeth 1hโ€ | Bot replies with real-time 1h chart-based summary | | System-wide trigger from another agent | Invokes webhook and returns response to parent workflow |


๐Ÿงพ Licensing & Attribution

ยฉ 2025 Treasurium Capital Limited Company Architecture, prompts, and trade report structure are IP-protected.

No unauthorized rebranding permitted.

๐Ÿ”— For support: Don Jayamaha โ€“ LinkedIn

Analyze Cryptocurrency Market Data with HTX API, GPT-4o, and Telegram

This n8n workflow provides an interactive way to analyze cryptocurrency market data using the HTX API, powered by GPT-4o (via OpenAI Chat Model) for intelligent insights, and delivered directly to you via Telegram. It allows users to query market information and receive AI-driven analysis.

What it does

  1. Triggers on Telegram Message: The workflow starts when a message is received via a configured Telegram bot.
  2. Initializes AI Agent: Sets up an AI Agent (LangChain) with a conversational chat model (OpenAI Chat Model) and a simple memory buffer to maintain context.
  3. Provides AI Tools: Equips the AI Agent with a "Calculator" tool for numerical operations and a "Think" tool for internal reasoning.
  4. Processes User Input: Takes the incoming Telegram message as input for the AI Agent.
  5. Generates AI Response: The AI Agent processes the input, potentially using its tools, to generate a relevant response or analysis.
  6. Formats Output: Prepares the AI-generated response for clear presentation.
  7. Sends Telegram Message: Delivers the AI's response back to the user via Telegram.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram bot token and chat ID. You'll need to create a bot via BotFather on Telegram.
  • OpenAI API Key: An API key for OpenAI, with access to models like GPT-4o (or other compatible chat models).
  • HTX API (Implicit): While not explicitly shown with an HTX node in the provided JSON, the workflow's intended purpose (analyzing crypto market data with HTX API) implies a need for HTX API access, likely integrated via the "AI Agent" through custom tools or prompts not detailed in the basic JSON structure. For a complete implementation, you would typically add an HTTP Request node or a custom tool within the AI agent to interact with the HTX API.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" -> "Import from JSON" and upload the file.
  2. Configure Credentials:
    • Telegram Trigger & Telegram Node:
      • Click on the "Telegram Trigger" node and then "Create New Credential" for Telegram API. Provide your Telegram Bot Token.
      • Do the same for the "Telegram" node.
      • For both Telegram nodes, ensure the "Chat ID" is correctly set to where you want the bot to listen and send messages.
    • OpenAI Chat Model Node:
      • Click on the "OpenAI Chat Model" node and then "Create New Credential" for OpenAI API. Provide your OpenAI API Key.
  3. Activate the Workflow:
    • Once all credentials are set up, click the "Activate" toggle in the top right corner of the workflow editor to make it live.
  4. Interact with the Bot:
    • Send a message to your configured Telegram bot. The AI Agent will process your query and respond.

(Note: The current JSON defines the core AI and Telegram interaction. To fully integrate HTX API for market data, you would need to add specific HTX API nodes or define custom tools within the AI Agent that can make HTTP requests to the HTX API based on user prompts.)

Related Templates

Automate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms

Overview Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Blueskyโ€”with easy expansion to more platforms. Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort. How It Works Two-Workflow Architecture: Content Aggregation Workflow Monitors Wallabag RSS feeds for tagged articles (to-share-linkedin, to-share-instagram, etc.) Extracts and converts content from HTML to Markdown Stores structured data in Airtable with platform assignment AI Generation & Publishing Workflow Scheduled trigger queries Airtable for unpublished content Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky) LLM generates optimized post text and image prompts based on custom brand parameters Optionally generates AI images and hosts them on Imgbb CDN Publishes via GetLate API (immediate or draft mode) Updates Airtable with publication status and metadata Key Features: Tag-based content routing using Wallabag's native system Swappable AI providers (Groq, OpenAI, Anthropic) Platform-specific optimization (tone, length, hashtags, CTAs) Modular designโ€”duplicate sub-workflows to add new platforms in \~30 minutes Centralized Airtable tracking with 17 data points per post Set Up Steps Setup time: \~45-60 minutes for initial configuration Create accounts and get API keys (\~15 min) Wallabag (with RSS feeds enabled) GetLate (social media publishing) Airtable (create base with provided schemaโ€”see sticky notes) LLM provider (Groq, OpenAI, or Anthropic) Image service (Hugging Face, Fal.ai, or Stability AI) Imgbb (image hosting) Configure n8n credentials (\~10 min) Add all API keys in n8n's credential manager Detailed credential setup instructions in workflow sticky notes Set up Airtable database (\~10 min) Create "RSS Feed - Content Store" base Add 19 required fields (schema provided in workflow sticky notes) Get Airtable base ID and API key Customize brand prompts (\~15 min) Edit "Set Custom SMCG Prompt" node for each platform Define brand voice, tone, goals, audience, and image preferences Platform-specific examples provided in sticky notes Configure platform settings (\~10 min) Set GetLate account IDs for each platform Enable/disable image generation per platform Choose immediate publish vs. draft mode Adjust schedule trigger frequency Test and deploy Tag test articles in Wallabag Monitor the first few executions in draft mode Activate workflows when satisfied with the output Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes. Technical Details 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs Prerequisites n8n instance (self-hosted or cloud) Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb Basic understanding of n8n workflows and credential configuration Time to customize prompts for your brand voice Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes. Category Tags social-media-automation, ai-content-generation, rss-to-social, multi-platform-posting, getlate-api, airtable-database, langchain, workflow-automation, content-marketing

Mikal Hayden-GatesBy Mikal Hayden-Gates
188

Ai website scraper & company intelligence

AI Website Scraper & Company Intelligence Description This workflow automates the process of transforming any website URL into a structured, intelligent company profile. It's triggered by a form, allowing a user to submit a website and choose between a "basic" or "deep" scrape. The workflow extracts key information (mission, services, contacts, SEO keywords), stores it in a structured Supabase database, and archives a full JSON backup to Google Drive. It also features a secondary AI agent that automatically finds and saves competitors for each company, building a rich, interconnected database of company intelligence. --- Quick Implementation Steps Import the Workflow: Import the provided JSON file into your n8n instance. Install Custom Community Node: You must install the community node from: https://www.npmjs.com/package/n8n-nodes-crawl-and-scrape FIRECRAWL N8N Documentation https://docs.firecrawl.dev/developer-guides/workflow-automation/n8n Install Additional Nodes: n8n-nodes-crawl-and-scrape and n8n-nodes-mcp fire crawl mcp . Set up Credentials: Create credentials in n8n for FIRE CRAWL API,Supabase, Mistral AI, and Google Drive. Configure API Key (CRITICAL): Open the Web Search tool node. Go to Parameters โ†’ Headers and replace the hardcoded Tavily AI API key with your own. Configure Supabase Nodes: Assign your Supabase credential to all Supabase nodes. Ensure table names (e.g., companies, competitors) match your schema. Configure Google Drive Nodes: Assign your Google Drive credential to the Google Drive2 and save to Google Drive1 nodes. Select the correct Folder ID. Activate Workflow: Turn on the workflow and open the Webhook URL in the โ€œOn form submissionโ€ node to access the form. --- What It Does Form Trigger Captures user input: โ€œWebsite URLโ€ and โ€œScraping Typeโ€ (basic or deep). Scraping Router A Switch node routes the flow: Deep Scraping โ†’ AI-based MCP Firecrawler agent. Basic Scraping โ†’ Crawlee node. Deep Scraping (Firecrawl AI Agent) Uses Firecrawl and Tavily Web Search. Extracts a detailed JSON profile: mission, services, contacts, SEO keywords, etc. Basic Scraping (Crawlee) Uses Crawl and Scrape node to collect raw text. A Mistral-based AI extractor structures the data into JSON. Data Storage Stores structured data in Supabase tables (companies, company_basicprofiles). Archives a full JSON backup to Google Drive. Automated Competitor Analysis Runs after a deep scrape. Uses Tavily web search to find competitors (e.g., from Crunchbase). Saves competitor data to Supabase, linked by company_id. --- Who's It For Sales & Marketing Teams: Enrich leads with deep company info. Market Researchers: Build structured, searchable company databases. B2B Data Providers: Automate company intelligence collection. Developers: Use as a base for RAG or enrichment pipelines. --- Requirements n8n instance (self-hosted or cloud) Supabase Account: With tables like companies, competitors, social_links, etc. Mistral AI API Key Google Drive Credentials Tavily AI API Key (Optional) Custom Nodes: n8n-nodes-crawl-and-scrape --- How It Works Flow Summary Form Trigger: Captures โ€œWebsite URLโ€ and โ€œScraping Typeโ€. Switch Node: deep โ†’ MCP Firecrawler (AI Agent). basic โ†’ Crawl and Scrape node. Scraping & Extraction: Deep path: Firecrawler โ†’ JSON structure. Basic path: Crawlee โ†’ Mistral extractor โ†’ JSON. Storage: Save JSON to Supabase. Archive in Google Drive. Competitor Analysis (Deep Only): Finds competitors via Tavily. Saves to Supabase competitors table. End: Finishes with a No Operation node. --- How To Set Up Import workflow JSON. Install community nodes (especially n8n-nodes-crawl-and-scrape from npm). Configure credentials (Supabase, Mistral AI, Google Drive). Add your Tavily API key. Connect Supabase and Drive nodes properly. Fix disconnected โ€œbasicโ€ path if needed. Activate workflow. Test via the webhook form URL. --- How To Customize Change LLMs: Swap Mistral for OpenAI or Claude. Edit Scraper Prompts: Modify system prompts in AI agent nodes. Change Extraction Schema: Update JSON Schema in extractor nodes. Fix Relational Tables: Add Items node before Supabase inserts for arrays (social links, keywords). Enhance Automation: Add email/slack notifications, or replace form trigger with a Google Sheets trigger. --- Add-ons Automated Trigger: Run on new sheet rows. Notifications: Email or Slack alerts after completion. RAG Integration: Use the Supabase database as a chatbot knowledge source. --- Use Case Examples Sales Lead Enrichment: Instantly get company + competitor data from a URL. Market Research: Collect and compare companies in a niche. B2B Database Creation: Build a proprietary company dataset. --- WORKFLOW IMAGE --- Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|-----------| | Form Trigger 404 | Workflow not active | Activate the workflow | | Web Search Tool fails | Missing Tavily API key | Replace the placeholder key | | FIRECRAWLER / find competitor fails | Missing MCP node | Install n8n-nodes-mcp | | Basic scrape does nothing | Switch node path disconnected | Reconnect โ€œbasicโ€ output | | Supabase node error | Wrong table/column names | Match schema exactly | --- Need Help or More Workflows? Want to customize this workflow for your business or integrate it with your existing tools? Our team at Digital Biz Tech can tailor it precisely to your use case from automation logic to AI-powered enhancements. Contact: shilpa.raju@digitalbiz.tech For more such offerings, visit us: https://www.digitalbiz.tech ---

DIGITAL BIZ TECHBy DIGITAL BIZ TECH
923

Automated weekly security audit reports with Gmail delivery

๐Ÿ”’ N8N Security Audit Report - Automated Weekly Email ๐ŸŽฏ What does this workflow do? This workflow automatically generates and emails a comprehensive security audit report for your N8N instance every week. It identifies potential security risks related to: Credentials ๐Ÿ”‘ : Exposed or insecure credentials Nodes ๐Ÿงฉ : Sensitive nodes (Code, HTTP Request, SSH, FTP, etc.) Instance settings ๐Ÿข : Global security configuration Community nodes ๐Ÿ“ฆ : Third-party nodes that may pose risks The report includes direct links to affected workflows, execution statuses, and actionable recommendations. --- โœจ Key Features ๐Ÿ“Š Smart Risk Assessment Calculates overall risk level: ๐ŸŸฉ Low / ๐ŸŸง Moderate / ๐ŸŸฅ High Tracks unique credentials (not just total occurrences) Provides detailed breakdown by node type ๐Ÿ”— Direct Workflow Links Clickable links to each workflow mentioned Shows last execution status (๐ŸŸข success / ๐Ÿ”ด failed) Displays execution timestamps ๐ŸŒ Bilingual Support Full support for French and English Switch language with a single variable ๐Ÿ“ง Beautiful HTML Email Clean, professional formatting Color-coded risk levels Emoji icons for easy scanning --- ๐Ÿš€ Quick Setup (5 minutes) 1๏ธโƒฃ Configure Credentials N8N API: Generate an API key in your N8N settings Gmail OAuth2: Set up OAuth2 for Gmail sending 2๏ธโƒฃ Set Your Variables Edit the "Set Config Variables" node: javascript { "email_to": "your.email@domain.com", "project_name": "My-N8N-Project", "server_url": "https://n8n.yourdomain.com", // NO trailing slash! "Language": "EN" // or "FR" } 3๏ธโƒฃ Test & Activate Click "Execute Workflow" to test Check your email inbox Activate for weekly automation --- ๐Ÿ“ง Example Report Output Subject: ๐Ÿ”’ Audit Report My-Project โ€“ Risk ๐ŸŸง Moderate Content: ๐Ÿ“Š Summary โ€ข Credentials involved: 8 (5 unique) โ€ข Nodes involved: 12 ๐Ÿ’ป code: 4 ๐ŸŒ httpRequest: 3 ๐Ÿ” ssh: 2 โ€ข Community nodes: 1 โ€ข Overall risk level: ๐ŸŸง Moderate ๐Ÿ” Credentials Risk Report ๐Ÿ”น Credentials with full access ๐Ÿ”‘ My AWS Credentials ๐Ÿ”‘ Database Admin ๐Ÿ“‹ Workflow: Data Processing Pipeline ๐ŸŸข (25-10-2024 06:15 โ†’ 06:16) ๐Ÿ’ป Process Data ๐ŸŒ API Call ๐Ÿงฉ Nodes Risk Report [...detailed node analysis...] --- ๐ŸŽจ Customization Options Change Schedule Modify the "Schedule Trigger" node to run: Daily at 8 AM Monthly on the 1st Custom cron expression Add Recipients Add multiple emails in the Gmail node's toList parameter Adjust Risk Thresholds Edit the JavaScript in "Format Audit Report" nodes to customize when risk levels change Use Different Email Service Replace Gmail node with: SMTP Microsoft Outlook SendGrid Any email service N8N supports --- ๐Ÿ’ก Use Cases โœ… Compliance Monitoring: Track security posture for audits โœ… Team Awareness: Keep your team informed of security status โœ… Change Detection: Notice when new risky nodes are added โœ… Best Practices: Get recommendations to improve security โœ… Multi-Environment: Run separate instances for dev/staging/prod --- ๐Ÿ”ง Technical Details Nodes Used: 8 Credentials Required: 2 (N8N API + Gmail OAuth2) External Dependencies: None N8N Version: Compatible with latest N8N versions Execution Time: ~10-20 seconds --- ๐Ÿ“‹ Requirements N8N instance with API access Gmail account (or other email service) N8N API key with audit permissions Valid SSL certificate for workflow links (recommended) --- ๐Ÿ› Troubleshooting Empty report? โ†’ Check your N8N API key has audit permissions Workflow links don't work? โ†’ Verify server_url is correct and has no trailing slash No execution status shown? โ†’ Workflows must have been executed at least once Wrong language displayed? โ†’ Set Language to exactly "FR" or "EN" (uppercase) --- ๐ŸŒŸ Why This Template? Unlike basic monitoring tools, this workflow: โœ… Provides context-aware security analysis โœ… Links directly to affected workflows โœ… Shows real execution data (not just theoretical risks) โœ… Calculates unique credential exposure (not just counts) โœ… Supports bilingual reports โœ… Delivers actionable recommendations --- ๐Ÿค Feedback & Support Found this helpful? Please rate the template! Have suggestions? Drop a comment below. Pro tip: Combine this with N8N's native alerting for real-time incident response! --- Tags: security audit monitoring compliance automation email reporting credentials governance --- ๐Ÿ“œ License MIT - Feel free to modify and share!

MatthieuBy Matthieu
389