Indicator or Strategy?
Choose the correct alert event for your script. Strategy order-fill alerts and indicator alerts are different sources of instructions; opening a trade manually on a chart does not create a webhook alert by itself.
Turn your TradingView webhook alerts into orders on a connected USDT-margined Binance Futures account. Configure symbols, trade size and exits in Copygram. The connection runs in the cloud, with no VPS required.
Prepare your Binance connection, create the webhook and Room, then verify the alert message and resulting receiver order. A TradingView alert is an instruction, not proof that Binance filled an order.
Copygram setup guide · TradingView webhook requirements · Symbol mapping guide · Troubleshoot rejected orders
Account
Add your USDT-margined Binance Futures account with an API key and secret. Enable Futures trading permissions and whitelist the connection IP shown in Copygram’s current documentation. Keep withdrawal permission disabled.
Route
Create a webhook in Copygram and select it as the source of a Room. Add Binance Futures as the receiver. Check the receiver’s symbol mapping, quantity, leverage and SL/TP settings, then copy the webhook URL.
Verify
Use a TradingView plan with webhook access and enable two-factor authentication. Paste the Copygram URL into the alert’s Webhook URL field. Follow the current message guide, then compare TradingView’s alert log, Copygram’s signal log and the Binance order result before relying on the automation.
| Symbol | Action | AI | Status |
|---|---|---|---|
| XAUUSD | Buy open | 87% | Executed |
| EURUSD | Sell open | 72% | Executed |
| GBPJPY | Close | – | Closed |
| USDJPY | Buy open | 45% | Skipped |
A reliable workflow starts with a clear instruction and a verified destination. Use the current Copygram message guide for your source.
Choose the correct alert event for your script. Strategy order-fill alerts and indicator alerts are different sources of instructions; opening a trade manually on a chart does not create a webhook alert by itself.
TradingView replaces supported placeholders when an alert fires. Strategy placeholders work only in strategy alerts. Inspect the actual direction, symbol and size sent; do not assume a backtest quantity matches your Binance receiver.
Start with the message format documented for Copygram. Confirm the parsed instruction, destination symbol and Binance order. A successful webhook delivery does not guarantee order acceptance or a particular fill price.
Set the behavior for each receiver before activating your Room. The same signal can require different quantities and symbols on different platforms.
Choose the receiver’s money management settings and check the resulting Binance order quantity. Configure SL/TP handling and how signals without those fields should be treated. Contract size, quantity limits and available margin still matter; do not transfer a forex lot example unchanged.
Set the Binance receiver’s leverage multiplier, or leave it blank to use the account’s default for that symbol. Leverage and order size are separate controls. Check both against the account’s limits before activation; increasing leverage does not improve the signal.
A TradingView chart can include an exchange prefix or contract suffix that differs from the receiver’s symbol. Map the incoming ticker to the exact supported Binance Futures instrument. Check the destination and signal log instead of assuming similarly named spot, CFD and futures products are interchangeable.
Configure whether the receiver follows close instructions and SL/TP modifications. Check how your strategy expresses entries, exits and reversals in the documented alert format. A sell instruction is not always equivalent to closing an existing long position; verify the intended result for your setup.
Use Symbol Lot Exceptions when an instrument needs a different size from the receiver default. These overrides take precedence over the main money management setting. Review the resulting Binance quantity and exposure for each symbol.
Where the incoming signal contains multiple take-profit levels, configure the percentage of the position assigned to each target. Check the percentages against the total position and Binance order limits. Confirm actual partial exits in the receiver account.
Use an always-on schedule or define the days and hours when the receiver accepts signals. Check the timezone shown in your settings. A connected Room can still skip a signal because of its schedule, filters or account requirements.
Check all receiver settings and current connection requirements. See all features →
Each destination has its own account, instrument and order requirements.
Create a Binance API key with Futures trading enabled and whitelist Copygram's IP address 13.134.78.72 when you create it.
There is no strict JSON schema: Copygram's AI works out the intent from the fields you send. The more fields you include, the more
predictable execution is. Plain-text commands like close EURUSD also work.
{
"action": "sell",
"symbol": "GBPJPY",
"volume": 0.01
} {
"action": "buy",
"symbol": "XAUUSD",
"volume": 0.10,
"sl": 2330.50,
"tp": 2365.00,
"signal_id": "tv_102938"
} {
"action": "close",
"signal_id": "tv_102938"
} | Field | Purpose | Example | Needed |
|---|---|---|---|
| action | What to do: open, modify, close, close half, move SL to breakeven | "buy" | Recommended |
| order_type | Direction and order type | "BUY LIMIT" | Recommended |
| symbol | Instrument to trade | "GBPJPY" | Recommended |
| volume | Lot size or contracts | 0.01 | Recommended |
| entry | Entry price, mainly for pending orders | 185.250 | Optional |
| sl | Stop loss price | 184.800 | Optional |
| tp | Take profit price | 186.500 | Optional |
| signal_id | Your ID for the trade, reused by later modify and close alerts | "qt_102938" | To modify or close later |
You only need a signal_id to modify or close a specific trade later. The opening alert defines it and every later
alert for that trade reuses it; let your strategy generate a unique ID per trade.
Every plan runs in the cloud with unlimited trade executions and Rooms. Save more than 50% by paying yearly.
Compare plansSupported accounts, webhook requirements, setup checks and subscription questions.
Connect a supported Binance Futures account, create a Copygram webhook and use it as a Room source. Add Binance as a receiver and configure its settings. TradingView sends the alert message to the webhook; Copygram processes the instruction and sends it to the receiver. Check each stage in the logs and confirm the resulting Binance order.
The documented connection supports USDT-margined Binance Futures. This page does not establish support for Binance Spot, COIN-margined contracts, Binance.US or Portfolio Margin. Confirm Futures access for your account and region, and ask support about any account type outside the setup guide.
Follow the current Copygram TradingView message guide and verify the resolved message in the signal log. TradingView can send plain text or JSON, but that alone does not establish that every message format is supported by the receiving service. Check the direction, symbol, size and exit instructions before using the alert.
Use a TradingView subscription with webhook access and enable two-factor authentication. Add the Copygram endpoint in the alert’s Webhook URL field. Strategy placeholders apply to strategy alerts; indicator alerts require the appropriate supported values. This workflow does not use email alerts as a substitute for webhooks.
Copygram’s guide requires an API key and secret, Futures trading permission and the connection IP listed in its documentation. Whitelist that IP and keep withdrawal permission disabled. Store credentials only in the account connection; do not put them in TradingView alert messages. Trade permission still authorizes orders that can lose money.
End-to-end timing varies with alert delivery, processing, account connectivity and Binance order handling. There is no fixed execution time promised here. A webhook can also fail or an order can be rejected. Compare the alert, signal and exchange records for your actual setup.
Check the Room status, parsed message, destination symbol, receiver schedule and filters. Then inspect API permissions, the IP whitelist, available margin and exchange quantity or order limits. Use the specific log or exchange error before changing settings or repeating an instruction.
Copygram does not offer a free trial. Compare the current monthly and discounted yearly plans on this page. TradingView subscriptions, exchange fees and trading losses are separate from Copygram’s subscription. Choose a plan with the webhook and account allowances your setup needs.
The configured webhook and Copygram Room run in the cloud. You do not need a local VPS for this connection. The source alert must remain active, credentials valid and services available. A local script, browser extension or other separate source can have its own device requirements.
A Room can use one webhook source and more than one receiver, within your plan allowances. Configure symbols and sizes independently for each receiver. If several Rooms share an account, review their positions and exit instructions to avoid unintended interactions.
Connect TradingView as the source, add your Binance Futures accounts and set the rules for each one. Copygram runs it in the cloud.