crypto market alert system with binance and telegram integration
Configured with Aggregate, Function, HTTP Request, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Messaging
- Transform
- Web / API
- 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.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Send Telegram Message | Messaging | Telegram | See node parameters |
| Aggregate | Transform | Aggregate | See node parameters |
| Binance 24h Price Change | Web / API | HTTP Request | See node parameters |
| Filter by 10% Change rate | Code | Function | See node parameters |
| Split By 1K chars | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Aggregate
Combine all items
Binance 24h Price Change
Get data of changed price coins in last 24h
Filter by 10% Change rate
Filter by 10% Up & Down
Split By 1K chars
Split them for telegram message limit
Workflow Setup Steps:
Workflow Setup Steps:
- Ensure the Schedule Trigger is active to desired cron time (Default 5 minutes).
- [Optional] Configure the Binance 24h Price Change node with your API details (Default one is Free Public API Call - Free).
- Set up your Telegram bot token in the Telegram node credentials.
- Update the Chat ID in the Send Telegram Message node.
- Test the workflow to ensure everything is set up correctly.
- Notes: Detailed telegram bot setup instructions are available in the workflow's n8n page.
crypto market alert system with binance and telegram integration
crypto market alert system with binance and telegram integration
Purpose and structure
This folder contains the crypto market alert system with binance and telegram integration workflow. Its executable nodes use aggregate, code, 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/Telegram/0381_Telegram_Code_Update_Webhook.json MIT; preserve source notices.