TradingView Webhook to Broker: Stocks, FX, Crypto Setup

Most people who wire a TradingView alert directly to a broker discover the same thing in the same order: the first fill works, the second one silently fails, and by the third they are debugging JSON at 2 a.m. with a half-filled position and no idea whether the exit alert made it through.

That is not a strategy problem. It is a plumbing problem. And plumbing is the part of retail algo trading that almost nobody talks about honestly, because the people selling "TradingView to broker" tutorials tend to have never traded a real six-figure account through one.

This is what actually happens when you route TradingView webhooks to a broker in 2026, what breaks, and why we ended up building SignalPipe as the boring middle layer that we needed ourselves. One subscription, two brokers, stocks and FX and crypto. That is the setup. Let's go.

Why raw TradingView webhooks break in live trading

TradingView alerts are a broadcast. They fire once. They do not know if the receiver caught the message, they do not retry, they do not queue, and they do not know what position you are currently in. That is fine for a Telegram ping. It is not fine for an order that moves real capital.

Here is what breaks when you point a TradingView alert directly at a broker's webhook endpoint:

1. The broker's endpoint is down for 400 milliseconds during a maintenance blip. Your alert is gone.
2. The alert fires while you are already in a position. TradingView does not know that. It sends the entry payload again. Your position doubles.
3. You get filled at a worse price than expected because the alert did not carry a limit price, so it defaulted to market during a spread blowout.
4. The exit alert fires. Your broker rejects it because the order-quantity field expected shares and TradingView sent a dollar value.
5. You wanted to scale in on a pullback. The raw alert has no concept of a safety-order ladder. It is one-shot only.

You might say: I will just add a Cloudflare worker in between. That is a valid objection, and honestly it is what I did for years. It works. It also means you are on call for your own plumbing forever, and every broker API change is your weekend.

The point of a managed execution engine is not that you cannot build it. It is that you should not have to.

What a managed webhook execution engine actually does

A webhook execution engine sits between TradingView and your broker and does the work that TradingView refuses to do and that brokers assume someone else has done.

• Idempotency: if the same alert fires twice in three seconds, only one order goes out.
• Position awareness: it knows what you are already holding on that symbol, so an entry alert during an open position gets rejected or scaled correctly.
• Retry logic: if the broker returns a transient error, the engine retries with backoff instead of throwing your alert in the bin.
• Order translation: it converts whatever payload TradingView sends into whatever the broker's API expects, including quantity math (dollars to shares to contracts).
• Logging: every alert, every order, every fill, every error stored so you can actually debug on Monday what went wrong on Friday.

None of this is glamorous. All of it is what separates a webhook setup that survives a full quarter from one that quietly goes offline and takes three trades with it before you notice. If you want the deeper walk-through of why raw payloads are not enough, the honest Alpaca guide covers the specific quirks on the stock side.

SignalPipe: one subscription, Alpaca and Capital.com routing

SignalPipe is what we built after running our own broker webhooks manually for too long. It is priced at exactly $29 per month, and it routes TradingView alerts to two brokers under one account: Alpaca for US stocks and crypto, and Capital.com for FX, indices, and CFDs.

The design goal was narrow on purpose. This is not trying to be every broker. It is trying to be the two brokers that cover most of what a retail systematic trader actually wants to trade, with a webhook layer that is production-grade rather than a weekend script.

What SignalPipe does:

• Accepts TradingView webhook JSON on a per-user endpoint
• Validates, deduplicates, and translates the payload
• Routes to Alpaca or Capital.com based on the symbol and account mapping
• Executes market, limit, or bracket orders as instructed by the alert
• Optionally layers a managed DCA ladder on top of a base entry
• Logs everything to a dashboard you can actually read

What SignalPipe does not do:

• It does not pick trades for you. Your TradingView script is the brain.
• It does not run its own strategies. That is what vyn premium is for.
• It does not connect to seventeen exchanges. Two brokers, on purpose.

No custom infrastructure, no cron jobs, no worker to babysit. Just an alert, a webhook URL, and a fill.

Stocks and 24/7 crypto via Alpaca: what works, what doesn't

Alpaca is the sensible choice for US retail algo traders because the API is stable, the fee structure is clean, and crypto trading is available on the same account as equities. That means one broker relationship, one funding source, and one webhook endpoint for both asset classes.

What works well through the Alpaca leg of SignalPipe:

• US equities during regular market hours, including fractional shares
• Extended-hours orders when you flag them explicitly in the alert
• Crypto orders 24/7 on the supported pairs
• Bracket orders with a stop and a target attached at entry

What is worth knowing before you route real money:

• Alpaca crypto coverage is narrower than a dedicated crypto exchange. If you trade obscure altcoins, this is not your setup.
• Extended-hours liquidity can be thin. A market order at 5 a.m. Eastern is not a market order, it is a donation.
• Regulatory rules on pattern day trading still apply to your Alpaca cash or margin account. Automation does not exempt you from that.

If you are trying to decide whether Alpaca as a whole makes sense for your setup, the honest Alpaca guide walks through the tradeoffs in detail. SignalPipe is the execution layer on top, not a substitute for choosing the right broker.

FX, indices, CFDs via Capital.com: order types and quirks

Capital.com is the other side of SignalPipe. It is a CFD broker, which means the instruments you trade there (FX pairs, indices, commodities, single-name CFDs) are contracts referencing the underlying, not the underlying itself. That has real consequences and I want to be direct about them.

The good part: Capital.com gives retail traders access to instruments that Alpaca does not cover. FX majors and minors, DAX, FTSE, gold, oil, and a broad list of equity CFDs. All of it through one API, all of it routable from a TradingView alert.

The parts that catch people:

• CFD positions carry overnight financing charges. If your strategy holds through a rollover, that cost is real and it eats into edge.
• Leverage is available but is not the same across instruments or jurisdictions. Retail leverage limits vary by regulator.
• Some instruments only quote during specific hours even if the underlying trades elsewhere. Your alert has to respect that.
• The spread is the fee, primarily. There is no per-share commission structure like Alpaca equities.

SignalPipe handles the mechanical part: order translation, position sizing based on your account currency, stop and limit placement in Capital.com's expected format. It does not tell you whether CFDs are the right vehicle for your strategy. That is a decision you make once, up front, based on what you are trying to do.

Managed DCA ladder vs plain alert-to-order

A raw alert-to-order flow does one thing: it sends one order per alert. If you want to scale into a position on a pullback, you need multiple alerts, careful position tracking, and enough discipline to not let a half-filled ladder confuse the exit logic.

The alternative is what we call a managed DCA ladder. One entry alert triggers a base order plus a pre-configured series of safety orders at defined price offsets, each with its own size multiplier. If price moves against the entry, the ladder fills automatically. If price recovers before the ladder is done, the unfilled steps are cancelled cleanly.

Here is how the two approaches compare in practice:

The managed ladder is not always better. If your strategy fires clean one-shot entries with a stop and target, a plain bracket order is simpler and more transparent. If your strategy scales in on drawdowns (the honest DCA case, which I covered in the DCA bot strategy piece), the managed ladder saves you from a category of bugs you should not be debugging.

No manual position tracking, no half-filled ladders, no exit alerts that reference orders you cannot find. That is the whole point.

Setup: from TradingView alert JSON to live fill in 15 minutes

The actual setup, end to end, is short. Here is the shape of it, without pretending it is a click-through tutorial (the docs handle that).

1. Create a SignalPipe account and connect either Alpaca, Capital.com, or both via API keys.
2. Copy your personal webhook URL from the SignalPipe dashboard.
3. In TradingView, create an alert on your strategy or indicator condition.
4. Paste the webhook URL into the alert's webhook field.
5. In the alert message box, write a JSON payload that names the symbol, side, quantity or dollar size, and optional stop and target.
6. Save the alert. Fire a test alert manually. Watch the fill appear in the SignalPipe dashboard and in your broker account.

The JSON schema is deliberately close to what an experienced TradingView user would guess. Symbol, side, quantity, order type, and optional bracket parameters. If you want a managed DCA ladder instead of a single order, you name the ladder preset in the payload and SignalPipe handles the multi-order logic on its side.

Fifteen minutes is not marketing. It is the honest number for someone who already has a TradingView Pro account, already knows what strategy they want to run, and already has funded broker accounts. If you are starting from zero on all three, budget a couple of hours, mostly for broker onboarding.

When SignalPipe is enough vs when you want vyn premium on top

This is the question I get most often, so let me be direct about it.

SignalPipe is the execution layer. It takes your TradingView alert and turns it into a broker order, reliably, with position awareness and optional DCA. It does not have an opinion about what to trade. Your strategy is your strategy.

vyn premium is a different product. It is our managed crypto strategy suite, built around Smart Safety Orders and the mechanics I described in the Smart Safety Orders write-up. It runs its own logic on connected exchanges. You are not writing the strategy, we wrote it. You are running it on your capital.

The clean way to decide:

• You have your own TradingView strategy or indicator, you trust it, and you want reliable execution to Alpaca or Capital.com: SignalPipe is enough. $29 per month, done.
• You want a rules-based crypto strategy that we run, with Smart Safety Orders and no per-asset tweaking: vyn premium.
• You want both: some traders run their own equity or FX strategies through SignalPipe and let vyn premium handle the crypto leg. That is a normal configuration.

There is no upsell trap here. SignalPipe stands on its own at $29 per month, forever, whether or not you ever look at vyn premium.

FAQ

Q: Do I need TradingView Pro for webhook alerts?

A: Yes. Webhook alerts are a paid TradingView feature. The free tier of TradingView does not support outbound webhooks, so any broker-routing setup, SignalPipe included, requires at least the entry paid plan.

Q: Can I use SignalPipe with a broker other than Alpaca or Capital.com?

A: Not today. The product is deliberately scoped to those two brokers because that is where we could ship a production-grade execution layer without cutting corners. Adding more brokers is a real engineering commitment and we would rather do two well than eight badly.

Q: What happens if my TradingView alert fails to send?

A: SignalPipe cannot execute what it never receives. TradingView is the sender, and if TradingView itself has an outage or throttles your account, no downstream tool can fix that. What SignalPipe can do is dedupe and retry on our side once the alert arrives, and log every attempt so you can see exactly what happened.

Q: Is SignalPipe automated trading in the regulatory sense?

A: You are the one placing the orders, using your own broker credentials, on your own account. SignalPipe is a tool that translates your alerts into API calls. It is not a discretionary manager, does not custody funds, and does not make trading decisions on your behalf. That said, the regulatory picture for retail algo tools varies by jurisdiction, so if you are unsure how it applies to you, ask someone qualified in your region.

Q: How does the managed DCA ladder differ from a grid bot?

A: A grid bot places buy and sell orders across a symmetric price range and profits from oscillation. A DCA ladder is directional: it scales into a position when price moves against the entry, with the assumption that the trade thesis remains valid. Different mechanics, different failure modes. Grids die in strong trends. DCA ladders die when the thesis was wrong and price keeps going.

Q: Can I run multiple TradingView strategies through one SignalPipe account?

A: Yes. Each alert carries its own payload, and SignalPipe routes based on what the payload says. You can have equity strategies going to Alpaca, FX strategies going to Capital.com, and crypto strategies going to Alpaca crypto, all through the same subscription.

Q: What is block algo flex and does it overlap with SignalPipe?

A: block algo flex is a separate free toolset included automatically with every blockresearch.ai app-web account. Different scope, different purpose. SignalPipe is specifically the TradingView-to-broker execution bridge, priced at $29 per month.

Risk disclaimer

Nothing in this article is financial advice. Automation removes the emotional part of order placement, it does not remove market risk. Any strategy that runs through SignalPipe is your strategy, and the outcomes are your outcomes. Backtests are not guarantees, past performance does not predict future performance, and leveraged instruments including CFDs can lose more than the initial margin depending on jurisdiction. If you are unsure whether any of this is appropriate for your situation, talk to someone qualified in your region before you route real capital.

The honest take

The plumbing between an alert and a fill is the part that separates strategies that live from strategies that quietly die. Most retail traders underestimate this until they have watched a missed exit turn a winning system into a losing month. I did. That is why we built SignalPipe in the first place, not as a product idea, but because we needed something that would not fail on us during a live position.

If you already have a TradingView strategy that you trust and you just want it to reach your broker reliably, SignalPipe at $29 per month is the boring, correct answer. One webhook engine, two brokers, stocks and FX and crypto covered. No custom infra, no worker to maintain, no half-filled ladders when an alert gets lost. That is the whole pitch.

If you do not yet have a strategy you trust, no execution layer will save you. Fix that first. Read the honest look at what makes a real backtest, pick a strategy whose mechanics you actually understand, and then come back to the plumbing. In that order.

Set up SignalPipe with your TradingView strategy when you are ready. The setup is fifteen minutes, the subscription is flat, and the plumbing stops being your problem.