Block 1 - When clicking ‘Execute workflow’
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
How it works Runs on a schedule and iterates a watchlist of symbols (e.g., BTC/ETH/SOL). For each symbol, request intraday 1h OHLCV from EODHD. A Code node computes Wilder’s RSI(14) and detects 30/...
n8n-nodes-base.manualtrigger, n8n-nodes-base.stickynote, n8n-nodes-base.set, n8n-nodes-base.splitout, n8n-nodes-base.splitinbatches, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Kevin Meneses .
Original n8n.io sourceHow it works
Runs on a schedule and iterates a watchlist of symbols (e.g., BTC/ETH/SOL).
For each symbol, request intraday 1h OHLCV from EODHD.
A Code node computes Wilder’s RSI(14) and detects 30/70 crossings.
When a signal appears, the bot sends a Telegram alert (HTML message) with price, RSI (prev → now), timestamp, and a “View chart” button that opens the pair on TradingView (BINANCE/USD).
Set up steps (≈10–15 min)
Prereqs: n8n (cloud or self-hosted), EODHD API key, Telegram bot + your chat_id.
Env vars: set EODHD_TOKEN and TELEGRAM_CHAT_ID on your n8n instance.
Credentials: add your Telegram credential (bot token).
Import the workflow JSON.
Edit Fields node: adjust the symbol array to your watchlist.
Schedule Trigger: choose how often to run (e.g., every 5–10 min).
Test: temporarily flip the Code node’s FORCE_ALERT flag to true to verify Telegram delivery, then set it back to false.
EODHD API Access the EODHD API with a 10% discount
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Crypto RSI alert system with EODHD, Telegram and TradingView charts |
|---|---|
| Complexity | advanced |
| Nodes | 15 |
| Categories | Crypto Trading, Multimodal AI |
| Author | Kevin Meneses |
| Published | 28 Aug 2025 |
Use the JSON export at /data/workflows/7997/7997.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works Runs on a schedule and iterates a watchlist of symbols (e.g., BTC/ETH/SOL). For each symbol, request intraday 1h OHLCV from EODHD. A Code node computes Wilder’s RSI(14) and detects 30/...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Crypto Trading, Multimodal AI use case.