Skip to main content

Monitor Binance futures funding rates and alert Telegram hourly

Workflow preview

Workflow preview
100%
Monitor Binance futures funding rates and alert Telegram hourly preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow runs hourly to scan Binance Futures USDT perpetual contracts, checks each symbol’s funding rate against warning and critical thresholds, and sends a formatted alert mes...

Best for

  • Crypto Trading automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.telegram, n8n-nodes-base.if, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.scheduletrigger, n8n-nodes-base.splitinbatches

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Đại Khiêm Như.

Original n8n.io source

1.1 Workflow description

Title
Monitor Binance futures funding rates and alert Telegram hourly
Workflow name
Monitor Binance futures funding rates and alert Telegram hourly

Quick Overview

This workflow runs hourly to scan Binance Futures USDT perpetual contracts, checks each symbol’s funding rate against warning and critical thresholds, and sends a formatted alert message to Telegram when any high funding rates are detected.

How it works

  1. Runs every hour on a schedule.
  2. Fetches all 24-hour ticker stats from the Binance Futures API.
  3. Filters for USDT perpetual pairs, excludes stablecoin and fiat-like symbols, sorts by 24h quote volume, and selects the top 20 tickers.
  4. For each selected symbol, calls Binance’s premiumIndex endpoint to retrieve the current funding rate and next funding time.
  5. Classifies each funding rate as normal, warning, or critical based on the configured thresholds and accumulates the results for the run.
  6. Builds an HTML-formatted Telegram message summarizing warning/critical symbols and sends it to your Telegram chat only when alerts are present.

Setup

  1. Create a Telegram bot, add the Telegram credentials in n8n, and set your target chat ID in the Telegram node.
  2. Adjust the schedule interval in the schedule trigger if you don’t want hourly checks.
  3. (Optional) Change the top-N selection and the warning/critical funding rate thresholds in the code steps to match your monitoring preferences.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Send Telegram Alert

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 3 - If Alerts Present

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 4 - Format Alert Messages

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 5 - Accumulate Funding Rate Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 6 - Fetch Ticker Funding Rate

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Sort and Select Top 20 Tickers

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Fetch Binance Tickers

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 9 - Every Hour Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 10 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Loop Over Tickers

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

3. Summary Table

Workflow Monitor Binance futures funding rates and alert Telegram hourly
Complexity intermediate
Nodes 14
Categories Crypto Trading
Author Đại Khiêm Như
Published 14 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16341/16341.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Monitor Binance futures funding rates and alert Telegram hourly do?

Quick Overview This workflow runs hourly to scan Binance Futures USDT perpetual contracts, checks each symbol’s funding rate against warning and critical thresholds, and sends a formatted alert mes...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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 use case.