summary: if your TradingView alert fired but nothing appeared in edgeful's trade notifications, the webhook URL isn't connecting the two properly — here's how to compare your URLs and fix the issue.
confirm the alert fired
before diving into webhook troubleshooting, make sure the alert actually triggered in TradingView:
open TradingView → click the clock icon on the right sidebar → click the log tab
verify the alert appears in the log for the session and instrument in question
if the alert isn't in the log, the issue is earlier in the chain — see TradingView alert didn't fire instead.
if the alert is in the log but nothing shows up in edgeful's trade notifications, the problem is the webhook connection between TradingView and edgeful.
compare your webhook URLs
the most common cause is a mismatch between the webhook URL in your TradingView alert and the one in your edgeful strategy. even a single character difference means the signal never reaches edgeful.
here's how to compare them:
step 1: copy the webhook from your TradingView alert
in TradingView, open your alerts panel and find the active alert for the algo. click to edit it and copy the full webhook URL from the webhook URL field.
step 2: copy the webhook from edgeful
in edgeful, go to the automation dashboard and find the strategy. the webhook URL is in step 2 of the setup flow.
you can either click the copy button beside "view webhook" — or click "view webhook" to open the popup and use the copy button there.
step 3: compare the two
paste both URLs side by side and confirm they match exactly. the full webhook URL should look something like this:
watch for truncated webhooks
this is a common gotcha. when copying the webhook URL, make sure you're getting the full URL — not a truncated version. TradingView and some browsers can visually cut off long URLs.
a truncated webhook looks something like this:
that's not usable — it's missing most of the URL. if your webhook looks like that, re-copy it using the copy button (not by selecting the text manually) and paste it into a text editor to verify the full string is there.
webhook pasted in the wrong field
the webhook URL must go in the webhook URL field in TradingView's alert settings — not in the alert message body. if it's pasted into the message box instead, TradingView won't send the signal to edgeful.
open your alert, check that the webhook URL field (at the bottom of the alert configuration) has the full URL, and that the message body doesn't contain the URL by mistake.
webhook changes when you create a new strategy
each edgeful strategy has its own unique webhook URL. if you deleted and recreated a strategy in the automation dashboard, the new strategy has a new webhook — and your TradingView alert is still pointing to the old one.
if you've recently recreated a strategy, copy the new webhook from step 2 of the automation dashboard and update your TradingView alert.
a note on alert processing delays
edgeful can only process alerts once they appear in TradingView's alert log. if an alert enters the log at 9:50 AM, that's when edgeful starts processing — any delay before that point is on TradingView's side, not edgeful's.
if you see a notification in edgeful but it arrived later than expected, check the timestamp in the TradingView alert log against the edgeful notification timestamp. the gap between them shows where the delay occurred.
still stuck?
if the webhook URLs match exactly and you're still not seeing notifications in edgeful, reach out via the in-app chat. have these ready:
a screenshot of your TradingView alert log showing the alert fired
the full webhook URL from your TradingView alert
the full webhook URL from your edgeful strategy
the team can compare the two on the backend and check if the signal is arriving but failing for another reason.