Does TradingView have a native Capital.com integration?

Yes. Open a TradingView chart, go to Charts, and select the Trading Panel section, then choose Capital.com and authorize the connection. It's a direct integration, not a third-party bridge, and it's been live since 2021.

Can I place automated trades on Capital.com through the Trading Panel?

No. The Trading Panel is discretionary order entry: you click buy, sell, or close, one order at a time, the same way you'd trade from Capital.com's own platform. Nothing about the panel connects to a TradingView alert or a Pine Script strategy signal.

If I run a Pine Script strategy, does it place real orders on Capital.com?

No. A strategy's orders are filled by TradingView's own broker emulator, a simulator, not a real broker. TradingView's own documentation says an alert fires when an order is executed by the broker emulator. The fill itself never leaves TradingView's servers.

How do I actually automate a Capital.com trade from a TradingView alert?

Point the alert's webhook at Autoview. A TradingView webhook only notifies an external app that an alert fired; it doesn't reach a broker by itself. Autoview is the app on the other end that turns the notification into a real order on your Capital.com account. TradingView is one sender among many: any system that can send a webhook can drive the same orders.

Capital.com on TradingView: native trading panel vs. automated alerts

Autoview · Guide · Updated October 3, 2026

Yes, TradingView connects to Capital.com. Capital.com is a native TradingView broker: you link your Capital.com account inside TradingView's Trading Panel and place trades by hand from the chart, with no third-party bridge. That connection has been live since 2021. What it doesn't do is trade for you. If you want an alert to open or close a Capital.com position on its own, that's webhook automation, and that's the part Autoview covers.

Which one you need comes down to who presses the button:

You, from the chart: use TradingView's Trading Panel. You don't need Autoview for that.
An alert or another system, without you: send a webhook to Autoview and it places the order on Capital.com. Start with connecting Capital.com to Autoview, or practice first on the Capital.com demo account.

What the native connection actually is

Open a TradingView chart, go to Charts, and select the Trading Panel section at the bottom of the page. Choose Capital.com, and if you're logged in you'll get an authorization pop-up; approve it and the two accounts are linked. From there, TradingView shows five tabs: Positions, Orders, History, Account Summary, and Notifications log.

Two Capital.com account types connect this way, each with its own symbol prefix in TradingView's symbol search:

CFD accounts use the CAPITALCOM: prefix, for example CAPITALCOM:EURUSD.
Spread betting accounts, available only in the UK and Ireland, use a separate CAPITALCOMSB: prefix.

Guaranteed Stop Loss is available on orders placed through the panel, and Capital.com's free demo account connects the same way as a live one, so you can test the panel itself with no funds at risk. TradingView's own broker profile for Capital.com, tradingview.com/broker/Capitalcom, is where TradingView itself documents the connection; Capital.com's own account types page is the source for which account type (CFD or spread betting) is available in your region, since Capital.com routes registration by residency to different regulated entities and doesn't make both products available everywhere.

The part that trips people up: it's discretionary, not automated

The Trading Panel is a manual order ticket. You click buy, sell, or close, one order at a time, the same way you would on Capital.com's own site or app. Nothing about the panel reads a TradingView alert or a Pine Script strategy signal and acts on it. If you're not sitting at the chart clicking the button yourself, the panel does nothing.

This is also true of Pine Script strategies specifically, which is the other place people expect execution to happen. TradingView's own documentation on strategy alerts states it plainly: an alert fires "when an order placed by the strategy is executed by the broker emulator." The broker emulator is TradingView's own simulator. A strategy backtest, and a strategy running in real time on your chart, both fill against that simulator, not against Capital.com, whether or not you've connected the Trading Panel at all.

Where a webhook fits, and where it doesn't

A TradingView alert can also fire a webhook, and this is the piece that's easy to assume does more than it does. Per TradingView's own webhook documentation, a webhook "notifies your external app when an alert is triggered." It sends an HTTP POST with the alert's message to a URL you configure. That's the entire job. The POST doesn't touch Capital.com, doesn't touch the Trading Panel connection, and doesn't place an order anywhere by itself. Something has to be listening on the other end of that URL and turn the notification into a real order.

TradingView also bounds the webhook itself pretty tightly: a three-second timeout on the receiving server's response, only ports 80 and 443 accepted, four fixed sender IP addresses (52.89.214.238, 34.212.75.30, 54.218.53.128, 52.32.178.7), and no IPv6 support.

Automating the trade: Autoview is the listener

Autoview is the app on the receiving end of that webhook. Connect your Capital.com account to Autoview, add an Autoview command to your TradingView alert's message, and point the alert's webhook URL at Autoview. When the alert fires, Autoview reads the command and places the order on Capital.com directly, no manual click and no broker-emulator simulation in between. TradingView is just one sender here. A TrendSpider alert, a Python script or your own server can post the same command to the same webhook. Autoview covers Capital.com CFD accounts and the Capital.com demo account; spread betting accounts, the UK/Ireland-only account type the native panel also supports, aren't part of Autoview's Capital.com connector.

Getting started with Capital.com on Autoview

Capital.com's own limits, if you're building around this

Capital.com's API sets its own bounds on how fast and how long a connection can run, independent of anything TradingView does:

A session token stays active for 10 minutes of inactivity before it expires and the next request errors out.
Order and position requests are capped at 1 per 0.1 seconds per user; faster than that and the request gets rejected.
The session-creation endpoint itself is limited to 1 request per second per API key.
A Demo account is capped at 1,000 requests per hour on order and position placement specifically.

None of these are Autoview-specific. They apply to any connection to Capital.com's API, including Autoview's, and they're worth knowing if you're firing alerts fast enough to hit them.

If you're checking a different broker

This page is scoped to Capital.com, since that's the specific native connection in question. The same shape of question comes up for other brokers too, and the answer isn't always the same: TradingView's native panel doesn't reach every broker, and even where it does, "connects" and "automates" are still two different questions. See does TradingView connect to Fidelity? for a broker where the native panel exists but automation, through Autoview or anything else, does not. Or see the Capital.com exchange page for what Autoview itself supports, or compare Autoview's extension and webhook platform if you're deciding how to automate in the first place.