Alerts And Webhooks
Add alert conditions and webhook-friendly alert messages to generated scripts.
Scribe Studio can add TradingView alert conditions to any generated script and draft webhook-ready JSON payloads for downstream automation. Both live inside the same chat — generate the indicator first, then ask Scribe to wire it for alerts.
Use Once Per Bar Close
When you create the TradingView alert from a Scribe-generated alertcondition(), set the trigger frequency to Once Per Bar Close. This matches the bar-close confirmation logic Scribe builds into its alerts by default and prevents intrabar duplicate fires. Selecting Once Per Bar or Only Once will produce different behavior than the script intends.
Alert Prompt Template
Add alert conditions to this indicator.
I need:
- Bullish alert when [condition].
- Bearish alert when [condition].
- Alerts should only trigger after bar close.
- Include clear alert names and messages.
Return the full updated script.
Webhook Prompt Template
Create a JSON webhook message for this TradingView alert.
Include:
- ticker
- timeframe
- signal side
- price
- bar time
- strategy or indicator name
Make the JSON valid and explain where to paste it in TradingView.
Bar-Close Confirmation In The Script
If you only want alerts to fire after a candle closes, state it clearly when you ask Scribe to build the alerts:
Only trigger alerts after the candle closes. Do not trigger intrabar alerts.
Then confirm in TradingView that the alert condition appears in the alert dialog and that you have selected Once Per Bar Close as the trigger frequency.
Test webhooks before going live
A bad webhook is worse than a missing one. Send a manual test fire from TradingView's alert dialog before connecting the alert to any broker, bot, or downstream automation. Verify the JSON parses, the fields populate with real values, and the receiver actually acts on the payload.