summary: set up TradingView for edgeful automation — from getting your invite-only indicator access through configuring futures contracts, enabling real-time data, and connecting your webhook for automated execution.

in edgeful, open the algos section and complete step 1 of onboarding. submit your TradingView username (not display name or email) — it's the one in your profile URL: tradingview.com/u/[your-username]. once submitted, open TradingView → indicators → invite-only scripts tab, and the edgeful algo indicators should appear there. full walkthrough below.

the account username from your profile URL, not your display name or email. find it by going to your TradingView profile — the URL will be tradingview.com/u/[your-username]. that [your-username] string is what goes in edgeful. entering the wrong one is the #1 reason indicators don't show up.

work through this list: (1) verify the username you submitted matches your TradingView profile URL exactly, (2) confirm you're logged into the right TradingView account on both platforms, (3) log out of TradingView and log back in, (4) give it a few minutes — access is usually immediate but can take a bit. still stuck? see my algo indicators aren't showing up in TradingView.

usually this means your all access subscription lapsed, or you switched TradingView usernames. re-authorize by re-submitting your current TradingView username in edgeful's algo onboarding. if your subscription is active and you're still locked out, reach out via in-app chat — see what happens if you lose TradingView indicator access for the full recovery flow.

yes to both if you're running live futures algos. TradingView Premium is the minimum plan that supports real-time data, and you need a separate CME real-time data package on top so your alerts don't fire on 10-minute delayed data. this is a TradingView requirement, not an edgeful one — even if you pay your broker for real-time data, TradingView needs its own data feed. see the "common questions" section below for the full answer on why.

no. once your algo is active in edgeful, it runs on edgeful's servers — not on your machine. your computer can be off, TradingView closed, and the algo will still execute. the only dependencies are an active all access plan, your broker connected with valid credentials, the algo set to active in edgeful, and an active TradingView alert with the edgeful webhook URL.

edgeful's algo indicators are invite-only TradingView scripts. before you can use them, you need to submit your TradingView username in edgeful so we can grant you access.

if they don't show up:

still stuck? see my algo indicators aren't showing up in TradingView.

when active on your chart, the algo indicators visualize 3 key levels:

having all 3 levels plotted visually lets you review the trade setup before the alert fires — you can see exactly what the strategy is planning before it executes.

edgeful currently offers 7 algo indicators in TradingView:

each indicator is built around a specific setup type. the initial balance and ORB indicators include variants with different exit logic — a standard version, a 2 take profit version (ORB), and a breakeven stop version that moves the stop to entry once the trade is in profit.

TradingView, edgeful, and your broker work together in 3 steps. you build and backtest your strategy in TradingView, then set up an alert with an edgeful webhook URL. when the alert fires, edgeful processes the signal and routes it to your broker (Tradovate, NinjaTrader, or ProjectX) for execution.

TradingView is used for 2 things in this pipeline: backtesting your strategy and hosting the alert that triggers the trade. it's not part of the execution path — edgeful handles that.

in strategy tester/strategy report, select your futures contract — e.g., ES1! (S&P 500 continuous contract) or NQ1! (Nasdaq). always use the continuous contract (1!) for backtesting because it automatically adjusts for rollovers. backtesting on single months introduces artificial gaps when contracts expire.

customize contract specifications: point value, tick size, and multiplier. for ES, that's $50 per point; for CL (crude oil), it's $1,000 per contract. these directly impact profit/loss calculations.

use regular candlesticks — not heikin ashi. heikin ashi candles cause order rejections because the calculated prices don't match actual market prices.

enter realistic commissions — most futures brokers charge $2–$5 round-trip per contract. use the fixed amount option in TradingView for accuracy rather than percentages. add slippage (0.5–2 ticks depending on liquidity and time of day) to simulate realistic fills.

TradingView's continuous contracts (ES1!, NQ1!) automatically adjust for rollovers when the front contract expires — your strategy doesn't need manual rollover logic.

check your broker's rollover schedule. some brokers auto-roll 5 days before expiration; others require manual action. verify this with your broker and note it in your trading plan. you'll want to make sure your TradingView alerts are set to the active contract to avoid execution issues.

contract symbols for alerts: when setting up alerts, use specific contracts — not continuous ones. a continuous symbol like GC1! changes which contract it points to during rollover. if your broker is on GCZ2025 but your alert fires on GC1! during rollover, your order gets rejected. use the specific month — e.g., GCZ2025 instead of GC1!, NQZ2024 instead of NQ1!. always make sure the alert symbol matches exactly what your broker has.

for the full breakdown, see futures contract rollovers.

by default, TradingView shows CME futures data with a ~10-minute delay. this isn't an edgeful issue — it's a TradingView data subscription thing. if you're running edgeful algos, delayed data means your alerts fire late, which means your entries are off.

to get live CME data, you need an active paid TradingView plan (TradingView Premium minimum) and a CME real-time data package. log into TradingView, go to account settings, find the market data subscription section, and purchase the CME real-time data package.

once it's active, your charts automatically switch to live data. you don't need to change any settings in edgeful or reconfigure your alerts — everything updates on its own.

after you've built and tested your strategy in TradingView, create an alert based on your strategy signals. in the alert settings, paste your edgeful webhook URL into the webhook URL field — this is how TradingView communicates with edgeful when a signal fires.

make sure the URL goes in the webhook URL field specifically — not pasted into the alert message body by mistake. a misconfigured webhook means missed or misrouted trades.

for the full alert setup walkthrough, see setting up TradingView alerts for algo automation.

edgeful automation works with 3 brokers: Tradovate, NinjaTrader (brokerage account), and ProjectX. connect your broker account in edgeful before enabling automation.

your broker connection needs to stay live — meaning your account needs to be active and funded. if your broker disconnects or your credentials expire, the algo will pause and you'll get a notification in the edgeful notification log.

no. once your algo is active in edgeful, it runs on edgeful's servers — not on your machine. you don't need TradingView open, your computer on, or to be watching the chart.

the only dependencies are: an active all access plan, your broker connected with valid credentials, the algo set to active in edgeful, and an active TradingView alert with a webhook URL pointing to edgeful.

use the strategy tester/strategy report to refine your algo before enabling live alerts. test in a demo account first — validate execution behavior before going live with real capital. start with micro contracts (MES, MNQ) before scaling to standard contracts.

monitor your broker connection and alert status regularly. check your broker's settlement rules and rollover schedules.

"I already pay for data through my broker — do I need to pay TradingView for data too?"

yes. TradingView's real-time data subscriptions are separate from your broker's data feed. even if you have real-time data through NinjaTrader or Tradovate, TradingView needs its own data subscription to fire alerts correctly.

this is a TradingView requirement, not an edgeful one. without real-time data on TradingView, your alerts may fire on delayed data — which means entries and exits won't align with actual market prices.

the good news: you don't need the most expensive data package. for US futures, the CME bundle on TradingView covers ES, NQ, YM, RTY, and most of the contracts edgeful algo users trade. check TradingView's data subscription page for current pricing.