# Feature request: TradingView connector for Perplexity Assistant

**URL:** <https://community.perplexity.ai/t/feature-request-tradingview-connector-for-perplexity-assistant/5610>\
**Category:** Feature Requests\
**Tags:** agent-api\
**Created:** [July 18, 2026, 12:40am UTC](https://community.perplexity.ai/t/feature-request-tradingview-connector-for-perplexity-assistant/5610 "2026-07-18T00:40:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hector1](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/hector1/32/3346_2.png) [@Hector1](https://community.perplexity.ai/u/Hector1)\
**Post date:** [July 18, 2026, 12:40am UTC](https://community.perplexity.ai/t/feature-request-tradingview-connector-for-perplexity-assistant/5610/1 "2026-07-18T00:40:34Z")

</div>

I’d like to request an official connector between Perplexity and TradingView.

## Use case

Many advanced traders use TradingView as their main signal layer (Pine Script strategies, indicators, alerts) and Perplexity as a research and decision co-pilot. An official connector would allow Perplexity to:

- Read TradingView alerts and chart context (symbol, timeframe, indicator outputs).
- Parse webhook payloads from TradingView and explain each alert in risk/position terms.
- Help design, review, and iterate Pine Script strategies using live chart context instead of manual copy-paste.
- Optionally hand off decisions to exchange/bot APIs (OKX, Bybit, Pionex, etc.) in a controlled, opt-in way.

## Why it matters

- Reduces friction for crypto and FX traders who currently copy/paste strategy code, screenshots, and alert logs into Perplexity.
- Creates a clean “TradingView → Perplexity → Exchange/Bot” workflow for analysis, documentation, and execution.
- Aligns with growing demand for AI-assisted quantitative trading, risk management, and backtesting.

## Suggested scope for a first version

1. TradingView webhook ingestion endpoint (read-only) for Perplexity Agents / API.
2. Ability to attach chart/alert context to a conversation or Agent workspace.
3. Clear security model: read-only by default, no order placement unless the user explicitly wires their own exchange/bot APIs.

I’m a professional user in crypto and financial markets and would be happy to provide concrete workflows and examples if helpful.