Fast answer
Crypto signal webhook-alert checks prove how an automated alert traveled from trigger to record.
Before accepting a webhook-driven signal result, record the trigger condition, alert message, webhook destination type, timestamp, payload fields, credential handling, retry behavior, execution system, and final close record.
If a provider says a webhook automated the trade but cannot show payload fields, trigger time, and final execution records, the automation proof is incomplete.
Automation checks
What to inspect in webhook-alert signal records.
Trigger condition
The alert should name the chart condition, script rule, or manual trigger that started the webhook.
Payload fields
The message should preserve pair, side, entry, stop, target, time frame, risk, and any routing fields.
Credential hygiene
Webhook messages should not expose exchange keys, bot tokens, passwords, or private account identifiers.
Delivery trail
Timestamps, receiving app logs, errors, retries, and final trade status need to stay attached to the record.
Source context
Webhook delivery is a transport layer, not a trading result.
TradingView explains that webhook alerts send an HTTP POST request when an alert triggers, while its alert documentation separates script alert triggers from the user-created alert. Crypto signal reviews should therefore preserve both the trigger logic and the delivery payload before treating automation as evidence.
Review standard
A reviewable webhook signal connects chart trigger, message payload, and final outcome.
For CSR evidence review, webhook-alert records should include original alert, chart or script trigger, payload, webhook destination type, timestamp, exchange or bot action, credential-safety notes, retries or failures, updates, and final status.