Page 3 of 3
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Wed Sep 23, 2026 9:30 am
by PTScalper
Replace the json_payload block in your script with this updated version:
Code: Select all
// Updated JSON Payload: Numeric values are now wrapped in quotes
json_payload = '{' +
'"Date": "' + str.format("{0,date,yyyy-MM-dd HH:mm}", t_entry_time) + '",' +
'"Pair": "' + t_pair + '",' +
'"Setup": "' + t_setup + '",' +
'"Outcome": "' + t_outcome + '",' +
'"Entry": "' + str.tostring(t_entry_price) + '",' +
'"Exit": "' + str.tostring(t_exit_price) + '",' +
'"StopLoss": "' + str.tostring(t_sl) + '",' +
'"Size": "' + str.tostring(t_size) + '",' +
'"RR": "' + str.tostring(realized_rr, "#.##") + '"' +
'}'
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Wed Sep 23, 2026 9:31 am
by PTScalper
Because Make previously received a broken payload, it is stuck expecting binary data. You must force it to re-read the clean JSON structure.
Re-determine Data Structure:
1.1.) Right-click your Custom Webhook module in Make and select Re-determine data structure.
1.2.) Verification: The webhook module will display a spinning animation, indicating it is waiting for new data.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Wed Sep 23, 2026 9:32 am
by PTScalper
2.Send a Clean Test Alert:
TradingView.Create a temporary manual alert (Alt+A) on any chart. Check the Webhook URL box and paste this perfectly formatted JSON into the Message box:{"Date": "2026-09-23 15:30", "Pair": "XAUUSD", "Setup": "15m Liquidity Sweep", "Outcome": "Win", "Entry": "2520.10", "Exit": "2525.50", "StopLoss": "2517.00", "Size": "1", "RR": "1.74"}
Verification: The spinning animation in Make will stop and display a green "Successfully determined" message.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Wed Sep 23, 2026 9:33 am
by PTScalper
3.Remap Google Sheets:
Open your Google Sheets module in Make. Click into each spreadsheet column field and re-map the green variables (Date, Pair, Setup, etc.) from the webhook payload.
Verification: The variables in the mapping menu will now appear as normal text strings instead of binary data collections.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Wed Sep 23, 2026 9:33 am
by PTScalper
4.Test the End-to-End Flow:
Click Run once in Make, send one more manual dummy alert from TradingView with the exact same payload, and check your Google Sheet.
Verification: The dummy trade metrics will populate cleanly into the individual columns in your spreadsheet.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Sat Oct 03, 2026 12:39 pm
by Fairman
Emotional state. Dropped it because it felt silly, then realised it was the field that explained the worst trades. Went back in pretty quickly.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Sat Oct 03, 2026 2:03 pm
by Fairman
The webhook into a sheet is clever, saves the copy paste that kills most journals by week three.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Sun Oct 04, 2026 2:27 pm
by LondonNewsTrader
PTScalper wrote: To fix the root cause, wrap all numeric variables in string quotes.
That fixes the content type, but it also turns every number into text, so the Sheet receives "1.0850" as a string and any formula has to convert it back. A cleaner fix is to send JSON null for missing values: build the field as na(sl) ? "null" : str.tostring(sl) with no quotes around it. null is valid JSON, TradingView keeps the application/json header, and Make maps it to an empty cell.
The diagnosis about the header is right. TradingView sends application/json only when the alert message parses as valid JSON, and text/plain otherwise, so one bad field changes how the whole payload is handled.
It's worth adding a test alert that fires with deliberately missing values before trusting the pipeline. The most common one is a stop or take profit that is na on a trade opened by a market order, which is exactly what you describe.
Re: The Minimum Fields Every Trade Journal Entry Needs
Posted: Thu Oct 29, 2026 8:14 am
by FXS Prop Desk
HansFX, there is a fair point in there: a journal that takes longer to fill than the trade took to execute will not survive long. Where a short record still earns its keep is in catching the slow changes you mention. If the market shifts, a few basic fields, entry time, pair, result in R, are enough to see when a setup that used to work has stopped. Without even that minimum, the change is felt in the account before it is seen anywhere else.