Does Pineflows place live orders on Robinhood today?

Not yet. As of September 2026 every alert is parsed, checked for instrument and duplicates, and recorded with the exact market order Pineflows will place, for example market buy 2 SPY. The broker connector that hands that order to Robinhood is the next release. Until it ships, every automation stays in test mode and nothing on this page should be read as a promise of fills today.

Do I need a third-party tool to send TradingView alerts to Robinhood?

Yes, for this workflow. The alert leaves TradingView as a webhook, an HTTP POST carrying your alert message, and something has to receive it, hold the broker connection and place the order. That is the bridge. TradersPost, SignalStack and Pineflows are webhook bridges; Quannected does the same job as a Chrome extension. They differ in brokers, assets, setup method, pricing and what they refuse to do by default.

Why did TradingView's Send test button not verify my automation?

For a strategy() or JSON message, Send test delivers the text with its {{placeholders}} unfilled, so the body arrives without an action, a quantity or a position. The adapter records it as unrecognized and keeps the body for review. An alert fired by the chart carries the real values, and that is what counts as the verified alert.

Do I need a paid TradingView plan?

Yes. Webhook notifications need a paid TradingView plan, and TradingView requires two-factor authentication on the account before the Webhook URL field under Notifications is available. If you are on the free plan you can still write and backtest the strategy, but the alert cannot reach Pineflows or any other alert-to-broker bridge.

Does Pineflows need my Robinhood password?

No. Pineflows never asks for a Robinhood password or a reusable token, not in the Claude chat and not in a form. Sign-in is Google only. Connecting Robinhood is part of the next release; until it ships there is nothing to hand over, and every automation runs in test mode.

What happens if TradingView sends the same alert twice?

Every parsed alert gets an event ID. For the default strategy message that is a hash of the body plus the minute it arrived; for the JSON message it is the alert time plus the order id. Pineflows keeps the last 200 event IDs per automation and records a repeat as duplicate, with nothing placed. The same guard runs in test mode, so you can watch it work first.

Can Pineflows short a stock or use limit orders?

No. Pineflows targets a Robinhood cash account: US equities and ETFs, long only, market orders. A short signal maps to a target of 0 shares, so the automation sells what it owns and never opens a short. Fractional quantities are allowed and the quantity mirrors what the alert carried. If you need options, crypto or stop orders, use another tool.

Guide · Updated September 17, 2026

Connect TradingView alerts to Robinhood. Keep the safety rails on.

To connect TradingView alerts to Robinhood, create one alert on the chart running your strategy, keep TradingView's default alert message, and paste a bridge's webhook URL under Notifications. Pineflows is that bridge: Claude builds the adapter from your Pine Script. Today Pineflows parses, verifies and records the market order it will place; live Robinhood execution is the next release.

Written by the Pineflows team

Pineflows is the Claude MCP connector that turns TradingView strategy alerts into recorded Robinhood market orders (live execution is the next release) with test mode, a duplicate guard and first-alert verification on by default. The team that built the adapter and pipeline described on this page wrote it. Published September 17, 2026.

In one sentence

Pineflows is a webhook bridge that turns TradingView alerts into Robinhood market orders for US equities and ETFs, set up in a Claude chat through the Pineflows MCP connector, with test mode, a duplicate guard and first-alert verification on by default. Today it parses, verifies and records the market order it will place; live Robinhood execution is the next release.

Setup · six steps

1
Create the automation in Claude
Add the Pineflows connector to Claude and sign in with Google. Paste your Pine Script into the chat. Claude classifies it, derives sample alert strings, validates the adapter against them, creates the automation in test mode, and returns a webhook URL ending in /api/webhooks/tv/<token>, plus the alert message to use.
2
Create the alert on the chart running your strategy
In TradingView, open the chart with your script applied, open the Alerts panel in the right sidebar and click Create alert. Under Condition, choose your strategy. Each automation handles one instrument, so the chart symbol must match the instrument Claude set.
3
Set the alert Message
For a strategy() script, keep TradingView's default message:
```
Order {{strategy.order.action}} @ {{strategy.order.contracts}} filled on {{ticker}}. New strategy position is {{strategy.position_size}}
```
If Claude gave you a JSON message to paste, replace the Message box with it exactly. For alert() or alertcondition() scripts, keep the text your script already emits.
4
Turn on Webhook URL under Notifications
Open the Notifications tab, enable Webhook URL and paste the Pineflows URL. This field requires a paid TradingView plan with two-factor authentication turned on. Set Expiration to open-ended, because an expired alert stops sending webhooks silently, and click Create.
5
Wait for one real fill, not Send test
Let the strategy fire once on the chart. Send test leaves {{placeholders}} unfilled, so a strategy or JSON message is recorded as unrecognized and does not count; only an alert fired by the script on the chart is the verification you want. When the real alert arrives, the signal log shows accepted_test with the parsed signal, for example target 2 SPY, and the automation is marked verified. Check that the ticker and quantity are what you expected.
6
Review the recorded orders; ask Claude to go live when the connector ships
Live requires one verified alert, Robinhood connected and an active plan, and only Claude sets it, when you ask. The Robinhood connector is the next release; until it ships, every automation stays in test mode and records the exact market order it will place. Pause is one button in the app at any time.

What goes wrong when you connect a trading bot to Robinhood?

Most people who search for how to connect a trading bot to Robinhood have already pictured the failure. A strategy fires an alert, the bot buys, the alert fires again on the next bar, the bot buys again, and by lunch there is a position nobody meant to hold.

The second fear is duplicates. TradingView can deliver the same alert more than once, and a bridge that treats every delivery as a new order turns one signal into two fills.

The third is the wrong ticker. You set the alert on one chart, the script is applied to another, and the order lands on a symbol you never backtested.

The fourth is credentials. Many bridges ask for a broker login or a long-lived token and store it. If that service is breached, or simply misbehaves, the bot has your account.

Pineflows was built around these four fears. Each one has a default that answers it, and the defaults are on before you touch anything.

Runaway loop: every automation starts in test mode, where alerts are parsed, verified and logged but no order is placed. Pause is one button in the app; from that moment every alert is recorded as blocked_paused and nothing is placed.
Duplicate orders: every parsed alert carries an event ID. Pineflows keeps the last 200 IDs per automation and a repeat is logged as duplicate and dropped.
Wrong ticker: one instrument per automation. An alert for any other symbol is recorded as wrong_instrument and never executed.
Credentials: Pineflows never asks for a Robinhood password or a reusable token, in chat or in a form. Sign-in is Google only.

How do TradingView alerts reach Robinhood?

TradingView can POST an alert's message to any HTTPS URL. That is the whole bridge: the alert fires, TradingView sends the message text to the URL in the alert's Webhook URL field, and a service at that URL has to turn the text into a broker order. Pineflows is that service for Robinhood.

With Pineflows the URL is unique to one automation and ends in /api/webhooks/tv/<token>. The token is the only credential, so treat it like a password. If it leaks, ask Claude to rotate it: a new URL is issued and the old one stops working.

The message text is parsed by an adapter into a signal: an instrument, an intent (a target position or a buy/sell delta), an event ID and a test flag. The signal is checked against the automation's instrument and its recent event IDs, then the pipeline computes the market order that gets the account from what it owns to what the signal asks for: target minus shares owned, with sells capped at what is owned.

Today the pipeline stops there and records that order, for example market buy 2 SPY, in the signal log. Nothing is sent to Robinhood. The broker connector that places the order is the next release.

What should the TradingView alert message be?

For a strategy() script, keep TradingView's default alert message. Pineflows reads it without any edit. The default message is:

Order {{strategy.order.action}} @ {{strategy.order.contracts}} filled on {{ticker}}. New strategy position is {{strategy.position_size}}

TradingView replaces each placeholder when the alert fires, so a real fill arrives as, for example, Order buy @ 2 filled on SPY. New strategy position is 2. Pineflows takes the instrument from the ticker and the target from the position after the fill; the action and contracts are matched but not acted on. Your Pine Script stays as you backtested it.

{{strategy.order.action}}: buy or sell, the side of the order the strategy just filled.
{{strategy.order.contracts}}: the size of that order. For an equity strategy this is the share count, fractional allowed.
{{ticker}}: the chart symbol, for example SPY or NASDAQ:QQQ. Pineflows drops the exchange prefix and compares the rest to the automation's instrument.
{{strategy.position_size}}: the position after the fill. Positive is long, 0 is flat, negative is short. This is the field Pineflows acts on; a negative value is clamped to 0 because the account is long only.
If your strategy needs order ids or an explicit test flag, Claude gives you a JSON message to paste instead; it carries {{timenow}}, {{strategy.order.id}} and {{strategy.market_position}} as well.
alert() and alertcondition() scripts keep whatever text they already emit. Claude writes case-insensitive rules that match those exact strings, first match wins, and runs sample alerts through them before anything is saved.

Does Pineflows place real Robinhood orders today?

No. As of September 2026 Pineflows does not place real Robinhood orders; it accepts the webhook, parses each alert, applies the duplicate guard, and records the exact market order it will place, for example market buy 2 SPY, in your signal log. The broker connector that sends that order to Robinhood is the next release.

Everything upstream of the broker is live now: the Claude setup, the adapter, the webhook, the duplicate guard, test and paused modes, first-alert verification and the signal log. That means you can wire a strategy up today, watch real alerts arrive, and see the exact orders that would have gone out before a single dollar is at stake.

Live mode is refused until three things are true: one verified real alert has arrived, Robinhood is connected, and the plan is active on trial or paid. You ask Claude to set the automation live; it never happens on its own, and Claude lists whichever prerequisite is missing. Because Robinhood cannot be connected yet, every automation stays in test mode today. When the connector ships, the automation you verified now goes live without a rebuild, under the same rules: market orders on US equities and ETFs, long only, quantity mirroring the alert.

What executes

01
Executes: US equities and ETFs on a Robinhood cash account.
No options, no crypto, no futures, no margin.
02
Executes: long entries and exits to flat.
A short signal, or any negative strategy position, maps to a target of 0 shares; Pineflows never opens a short.
03
Executes: market orders only, fractional quantities allowed.
Pineflows places no limit, stop or bracket orders; exits come from your script's alerts.
04
Quantity mirrors the alert.
A default quantity is used only when the alert carries none; an alert with no quantity and no default is recorded as missing_quantity and never executed.
05
One instrument per automation.
An alert for another ticker is recorded as wrong_instrument and never executed.
06
A repeated event ID within the last 200 events per automation is recorded as duplicate and ignored.
Once an event is consumed it is never re-run.
07
Every automation starts in test mode.
Live requires one verified real alert, Robinhood connected and an active plan, trial or paid, and is set only by asking Claude.
08
There is no sandbox at the broker.
Test mode is the sandbox: alerts are parsed, recorded and verified without orders.
09
As of September 2026, no order reaches Robinhood.
The pipeline records the exact market order it will place; live Robinhood execution is the next release.
10
TradingView's Send test button leaves {{placeholders}} blank, so a strategy or JSON message sent that way is recorded as unrecognized and does not verify the automation.
11
Webhook alerts require a paid TradingView plan with two-factor authentication enabled.
12
Pineflows never asks for your Robinhood password or a reusable token, in chat or in a form.

Why does TradingView's Send test button not count?

Send test delivers the alert message without expanding its placeholders. The body that reaches Pineflows carries no action, no contracts and no position, so the default strategy pattern does not match and the alert is recorded as unrecognized with the raw body kept for review.

An unrecognized alert never verifies the automation. Verification means a real alert, fired by your strategy on the chart, parsed by the adapter into the signal you expected. That is the only evidence Pineflows accepts before live mode is allowed.

Send test is still useful for one thing: the log row proves TradingView delivered to the right URL. It just does not verify the adapter. Every alert that reaches a valid webhook URL becomes one row in the signal log with a fixed outcome, so you can read the log without guessing.

unrecognized: the alert did not match the adapter. Raw body kept for review, truncated to 2 KB.
wrong_instrument: the alert's ticker does not match this automation's instrument. Never executed.
missing_quantity: a rule matched but no quantity and no default quantity was available. Never executed.
duplicate: an event ID seen within the last 200 events. Ignored.
blocked_paused: the automation is paused. Nothing placed.
accepted_test: parsed and verified in test mode, with the signal it produced, for example target 2 SPY. No order placed. This is the row that marks your automation verified.
order_submitted, order_rejected, order_unknown: live-mode outcomes for when the broker connector ships. An event is consumed the first time it is processed and is never re-run, whatever happens after.

Which tool should I use to connect TradingView to Robinhood?

Pick by what you trade and by how you want setup to happen. TradersPost, SignalStack and Pineflows all receive a TradingView webhook; Quannected works as a Chrome extension instead, and PickMyTrade is built around futures platforms and a multi-account copier. They differ on brokers, assets, who writes the mapping from alert text to order, pricing, and what happens by default before you switch anything on. Every cell in the table below is something you can check on each vendor's own site.

Pineflows loses on breadth: it connects one broker, trades two asset classes, and does not execute yet. It is different in one specific way: there is no field mapping. Claude reads the Pine Script and builds the adapter from it, checks sample alerts against it, and creates the automation in test mode with a duplicate guard and a required verified alert before live.

Scroll sideways

Tool	Brokers	Assets on Robinhood	Setup method	Pricing model	Safety defaults
Pineflowsthis site	Robinhood only. Today records the order it will place; live execution is the next release.	US equities and ETFs, long only, market orders, fractional ok. No options, crypto or futures.	Claude reads your Pine Script and builds the adapter in chat; no field mapping.	One plan, Pineflows Pilot, monthly via Stripe. 7-day free trial, no card to start.	Test mode first, duplicate guard, one instrument per automation, one verified real alert required before live, one-button pause. No broker-side stops.
TradersPost	Many brokers including Robinhood; takes TradingView and TrendSpider alerts. Executes on Robinhood today.	Stocks, stock options, index options, crypto. No futures via Robinhood.	TradingView or TrendSpider alert via webhook.	Free 7-day trial.	Paper trading; stop loss, take profit and trailing stops; fractional shares.
SignalStack	33+ brokers including Robinhood.	Not stated per asset on the pages we checked.	Choose platform, connect broker, set order directions, paste link into the alert. No coding required.	Not verified for this page.	Not stated on the pages we checked; claims execution under 0.45 s.
PickMyTrade	Futures-oriented: Tradovate, Rithmic, IBKR, TradeStation, ProjectX, 27+ prop firms. Robinhood not listed.	Robinhood not listed.	Multi-account copier; setup method not verified for this page.	Flat $50.	Not stated on the pages we checked.
Quannected	Robinhood, via a Chrome extension.	Not stated on the pages we checked.	Chrome extension that bridges TradingView alerts to Robinhood.	Not verified for this page.	Not stated on the pages we checked.

If you trade options or crypto, or want broker-side stop-loss or take-profit orders, pick TradersPost; if you run more than one broker or need live Robinhood fills this week, TradersPost or SignalStack. Pineflows is for a long-only equity strategy you want run with the safest possible defaults.

You trade options or crypto on Robinhood, or want broker-side stops: TradersPost. On Robinhood it supports stocks, stock options, index options and crypto, with no futures; it offers live and paper trading, fractional shares, and stop loss, take profit and trailing stops.
You run several brokers and want a no-code setup: SignalStack. It lists 33+ brokers including Robinhood, requires no coding, and claims execution under 0.45 s.
You copy futures trades across several accounts or prop firms: PickMyTrade. Flat $50 pricing, a multi-account copier, built around Tradovate, Rithmic, IBKR, TradeStation, ProjectX and 27+ prop firms. Robinhood is not listed on the pages we checked.
You want a browser extension: Quannected, a Chrome extension that bridges TradingView alerts to Robinhood.
You have a backtested Pine Script strategy, trade US equities or ETFs on Robinhood, and would rather paste the script into Claude than map fields in a dashboard: Pineflows. Today it parses, verifies and records every order it will place; live Robinhood execution is the next release.

What does Pineflows cost?

One plan, Pineflows Pilot, billed monthly through Stripe. There are no tiers and no per-broker or per-alert pricing.

A 7-day free trial starts the first time Claude connects or you open the app after onboarding, whichever comes first. No card is needed to start, and you can cancel from the billing portal at any time.

Only live mode checks the plan. You can wire up and verify a strategy in test mode before deciding whether to pay.

On top of any bridge, TradingView webhooks need a paid TradingView plan with two-factor authentication turned on. The free plan cannot send webhooks, so a free account cannot reach Pineflows or any other alert-to-broker bridge.