Skip to main content

Monitor futures trades and send risk alerts using Binance, Sheets, Slack and email

Workflow preview

Workflow preview
100%
Monitor futures trades and send risk alerts using Binance, Sheets, Slack and email preview
Open on n8n.io

1. Workflow Overview

Futures Trade Monitoring & Risk Alert Workflow n8n, Binance API, Google Sheets, Slack, Telegram, Jira & Email This workflow automates futures trade monitoring by fetching live prices from Bina...

Best for

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

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.merge, n8n-nodes-base.if, n8n-nodes-base.switch, n8n-nodes-base.googlesheets, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.

Original n8n.io source

1.1 Workflow description

Title
Monitor futures trades and send risk alerts using Binance, Sheets, Slack and email
Workflow name
Monitor futures trades and send risk alerts using Binance, Sheets, Slack and email

Futures Trade Monitoring & Risk Alert Workflow

> n8n, Binance API, Google Sheets, Slack, Telegram, Jira & Email

This workflow automates futures trade monitoring by fetching live prices from Binance, calculating trade performance (PnL, ROI, fees), evaluating risk levels and sending alerts across Slack, Telegram, Jira and Email. It also stores trade history and analytics in Google Sheets.

Quick Implementation Steps

  1. Import workflow into your n8n account.
  2. Configure trade input (Function or Google Sheets).
  3. Connect Slack, Telegram, Jira, Gmail credentials.
  4. Set up Google Sheets (Trades & Analytics).
  5. Run workflow or enable schedule trigger.

What It Does

This workflow continuously monitors futures trading positions by combining user-defined trade data with real-time market prices fetched from the Binance public API. It calculates key metrics such as profit/loss (PnL), return on investment (ROI) and transaction fees to evaluate trade performance.

Based on calculated values, the workflow applies a risk scoring mechanism to classify trades into different severity levels. These levels determine how alerts are routed across communication platforms such as Slack, Telegram, Jira and Email.

Additionally, the workflow stores all trade data and daily analytics in Google Sheets, enabling users to track performance trends and maintain a history of trades without manual effort.

Who It's For

  • Crypto futures traders
  • Trading teams and analysts
  • Risk management teams
  • Automation enthusiasts using n8n
  • Developers building trading dashboards

Requirements

  • n8n account (cloud or self-hosted)
  • Binance public API access (no API key required)
  • Google Sheets account
  • Slack workspace (optional)
  • Telegram bot (optional)
  • Jira account (optional)
  • Gmail account (optional)

How It Works & Setup Instructions

Step 1: Trigger Setup

Configure Schedule Trigger to run at intervals (e.g., every 5 minutes).

Step 2: Trade Input

Use Function node or Google Sheets to define:

  • symbol
  • entry_price
  • quantity

Step 3: Fetch Market Data

HTTP Request node calls Binance API:

  • Endpoint: /api/v3/ticker/price

Step 4: Merge Data

Merge node combines trade input with live price.

Step 5: Process Trade Metrics

Function node calculates:

  • PnL
  • Fees
  • Net PnL
  • ROI

Step 6: Filter Valid Trades

IF node ensures valid calculations (e.g., non-null values).

Step 7: Risk Scoring

Assigns risk score based on loss and position size.

Step 8: Alert Routing

Switch node routes alerts:

  • Low → Slack
  • Medium → Slack + Telegram
  • High → Slack + Telegram + Jira + Email

Step 9: Store Trade Data

Google Sheets (Trades):

  • Stores trade history

Step 10: Analytics

Function node generates:

  • Daily trade count
  • Net PnL summary

Step 11: Store Analytics

Google Sheets (Analytics):

  • Stores summarized data

How To Customize Nodes

  • Modify Function node to change trade input logic.
  • Adjust HTTP Request node for different APIs.
  • Update PnL logic for leverage or futures margin.
  • Modify risk scoring thresholds.
  • Customize alert messages per platform.
  • Change Google Sheets structure as needed.

Add-ons (Extend Functionality)

  • Duplicate alert prevention using Google Sheets lookup
  • Dashboard integration (Google Data Studio / Power BI)
  • Auto trade sync via exchange APIs
  • Webhook-based real-time alerts
  • Error handling and retry logic

Use Case Examples

  1. Monitor crypto futures trades in real time.
  2. Receive instant alerts for high-risk positions.
  3. Track daily profit/loss automatically.
  4. Manage multiple assets without manual checking.
  5. Enable centralized monitoring for trading teams.

Note: This workflow can be adapted for many other financial monitoring and automation use cases.

Troubleshooting Guide

Issue Possible Cause Solution
PnL is null Incorrect field mapping Ensure correct price field is used
Telegram error Formatting issue Set Parse Mode to NONE
No alerts triggered Risk condition not met Check Switch node logic
Empty rows in Sheets Wrong data source Connect correct node to Sheets
API error Invalid request Verify Binance endpoint

Need Help?

If you need help setting up, customizing or extending this workflow, feel free to reach out our n8n workflow developers at WeblineIndia.

We can help you:

  • Customize workflows
  • Integrate additional APIs
  • Build scalable automation systems
  • Add advanced analytics and dashboards
  • And so much more.

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 - Schedule Trades Check

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

Block 2 - Trade Positions

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

Block 3 - Market Price (Binance)

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

Block 4 - Trade + Market Data

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 5 - Valid Trades Only

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

Block 6 - Risk Scoring Engine

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

Block 7 - Alert Severity Split

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.4

Block 8 - Trade History

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 9 - Execution Summary

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 10 - Daily Analytics

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

Block 11 - Analytics Summary

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 12 - Slack (LOW RISK)

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 13 - Slack (MEDIUM RISK)

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 14 - Telegram (MEDIUM RISK)

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

Block 15 - Slack (HIGH RISK)

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

Block 16 - Jira (HIGH RISK)

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

Block 17 - Telegram (HIGH RISK)

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

Block 18 - Gmail (HIGH RISK)

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 19 - PROCESS - Trade Metrics Engine

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

Block 20 - Sticky Note

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

Block 21 - Sticky Note1

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

Block 22 - Sticky Note2

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

Block 23 - Sticky Note3

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

3. Summary Table

Workflow Monitor futures trades and send risk alerts using Binance, Sheets, Slack and email
Complexity advanced
Nodes 23
Categories Crypto Trading
Author WeblineIndia
Published 27 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15329/15329.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 futures trades and send risk alerts using Binance, Sheets, Slack and email do?

Futures Trade Monitoring & Risk Alert Workflow n8n, Binance API, Google Sheets, Slack, Telegram, Jira & Email This workflow automates futures trade monitoring by fetching live prices from Bina...

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.