← All N8N workflows
Messaging & emailFunctionHTTP RequestSchedule TriggerTelegram

πŸ“Œ Daily Crypto Market Summary Bot

Configured with Function, HTTP Request, Schedule Trigger, Telegram. Review the connections and setup before adapting this template.

Workflow preview
TriggerSchedule TriggerSchedule TriggerWeb / APIBinance 24h PriceChangeHTTP RequestMessagingSend Telegram MessageTelegramCodeAnalyze & Format MarketDataFunction

Node categories in this workflow

  • Trigger
  • Web / API
  • Messaging
  • Code

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and βˆ’ to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Schedule TriggerTriggerSchedule TriggerSee node parameters
Binance 24h Price ChangeWeb / APIHTTP RequestSee node parameters
Send Telegram MessageMessagingTelegramSee node parameters
Analyze & Format Market DataCodeFunctionSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • telegramApi

Workflow notes

Binance 24h Price Change

Get data of changed price coins in last 24h

πŸ“Œ Daily Crypto Market Summary Bot

πŸ“Œ Daily Crypto Market Summary Bot

πŸ“ˆ What It Does

Fetches hourly 24h price data from Binance for BTC, ETH, and SOL (USDC pairs), analyzes key market trends, and sends a well-formatted HTML summary to a Telegram chat.


πŸ“Š Metrics Analyzed

  • πŸ”Ί Gainers / πŸ“‰ Losers
  • πŸ’° Price change %
  • πŸ“ˆ Volatility (High vs Low)
  • βš–οΈ Bid-Ask Spread %
  • πŸ”Ό Momentum (vs Weighted Avg)
  • ⭐ vs Market Average
  • πŸ”’ Number of Trades

⚠️ Notes

  • Message output is automatically split into chunks to stay under Telegram’s 4096 character limit.
  • Output is sent in rich HTML format for better readability.

βœ… This note is for internal guidance. Feel free to delete or update it after setup.

πŸ› οΈ Setup Instructions

πŸ› οΈ Setup Instructions

  1. Telegram
    • Create a bot via @BotFather
    • Add the bot to a Telegram group or use a personal chat
    • In the Send Telegram Message node:
      • Add your bot token under credentials
      • Replace the default chatId with your group/user chat ID
Sticky Note2

Binance

  • No Binance API key required (uses public endpoint)
  • Ensure internet access to call Binance API
⏱ Schedule

⏱ Schedule

  • Runs every hour
  • Cron expression: 5 * * * *
    (At minute 5 of every hour)
Sticky Note4
  1. Optional: Add More Coins
    • In the Function node, find the line:
      const relevantSymbols = ['SOLUSDC', 'BTCUSDC', 'ETHUSDC'];
      
    • Add your preferred trading pairs (must end in USDC)
πŸ“Œ Daily Crypto Market Summary Bot

πŸ“Œ Daily Crypto Market Summary Bot

Purpose and structure

This folder contains the πŸ“Œ Daily Crypto Market Summary Bot workflow. Its executable nodes use function, httpRequest, scheduleTrigger, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Schedule Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0870_HTTP_Schedule_Update_Webhook.json MIT; preserve source notices.

More in Messaging & email