TradingView Webhook Automation

When a TradingView alert fires, the webhook delivers the alert payload to the configured endpoint. The payload can include information such as symbol, action, strategy, timeframe, quantity, and price context.

The webhook itself does not know whether the account is ready, whether the strategy is enabled, or whether the message is a duplicate. Those decisions belong to the receiving execution system.

Consistent field names make alerts easier to validate and audit. A stable message format also reduces the chance that a strategy update silently changes the meaning of an instruction.

TradeLuma uses strategy-specific workflows so the incoming alert can be matched to the expected symbol, direction, broker connection, and execution settings.

Webhook systems can encounter retries or repeated alerts. Without duplicate handling, the same trading intent may be submitted more than once.

A controlled workflow uses identifiers and deduplication rules to reduce accidental repeated orders while still keeping blocked or duplicate messages visible for review.

Receiving an alert is only the beginning of the execution path. The important operational questions are whether the instruction passed validation, whether the broker accepted it, and what final status the broker reported.

TradeLuma keeps the alert-to-order path visible so the user can review acceptance, blocking, submission, fills, cancellations, and broker-side outcomes.