When an alert does not land in Telegram, the cause is usually one of a handful of things. Work down this list in order — the alert log in AlertSync tells you which one it is without guessing.
If a TradingView webhook is not delivering to Telegram, check these in order: the webhook URL is pasted correctly into the alert's Webhook URL field (a wrong id returns a 404); the webhook is active and not paused — a webhook you turned off returns 403, and one that hit your monthly alert quota is auto-paused and records the alert as dropped; the AlertSync bot is still a member of the group, or an admin with posting rights in the channel; and your TradingView plan actually allows webhook alerts, since TradingView restricts that feature to paid tiers. The alert log on your dashboard records every incoming alert with its status and the exact error, so it shows you which of these applies.
Open the TradingView alert, check the Webhook URL field, and compare it character for character with the address on the webhook's card. A single wrong or missing character in the id means the alert reaches a webhook that does not exist — AlertSync returns a 404 and nothing is delivered. Re-copy and re-paste the whole URL to be sure.
On the dashboard, make sure the webhook shows as Active. A webhook you switched off by hand refuses incoming alerts with a 403. A different kind of pause happens automatically when you hit your monthly alert quota — the webhook is paused and each blocked alert is recorded as dropped, then it resumes on its own when your quota resets or you upgrade.
If the bot was removed from a group, or a channel's permissions changed, that destination fails while any others still receive the alert. For a channel the bot must be an administrator with the Post Messages permission — groups usually just need it as a member. Re-add or re-promote the bot and delivery resumes.
If the Webhook URL option is greyed out or the alert never seems to fire a POST at all, confirm your TradingView subscription includes webhook notifications. TradingView limits that feature to its paid tiers; nothing on the AlertSync side can add it, because the alert never leaves TradingView in the first place.
Open the webhook's detail panel and look at the alert log. Every incoming alert is recorded with a status — delivered, failed or dropped — the destinations it targeted, how many failed, and the exact error Telegram returned. That turns 'it is not working' into a specific cause you can fix.
The log is the fastest way to diagnose a problem because it distinguishes causes that otherwise look identical from TradingView's side:
A common cause is the bot quietly losing access to a destination. In a group the bot usually posts as an ordinary member, but if the group restricts who may send messages it must be an admin. A channel always requires the bot to be an administrator with posting rights — Telegram does not allow non-admins to post there. If a destination upgraded from a group to a supergroup, its internal id can change; remove and re-add it.
Two causes sit entirely outside AlertSync. First, TradingView's paid-plan requirement for webhooks — if your plan does not include them, the alert never fires a POST. Second, the alert condition itself: a TradingView alert set to Once Per Bar Close only fires when the bar closes, so a condition that looks true intraday may not have triggered yet. Send /test to the bot to prove the AlertSync-to-Telegram leg works independently of TradingView.
The full walkthrough covers the whole flow end to end with screenshots of every screen — creating the webhook, linking Telegram with a six-digit code, and pasting the URL into a TradingView alert.
Read the setup guide →A 404 means the URL points at a webhook that does not exist — almost always a mistyped or partially copied id, or a webhook that was deleted. Re-copy the full https://alertsync.in/hook/ address from the webhook card and paste it into the TradingView alert again.
Check two things first. If the alerts show as dropped in the log, you hit your monthly quota and the webhook auto-paused — it resumes when the quota resets or you upgrade. If they show as failed, the bot likely lost access to a destination, such as being removed from a group or losing admin rights in a channel.
If there is no entry in the AlertSync alert log, the POST never reached us — check the Webhook URL is correct and that the alert's Webhook URL action is actually ticked. If there is an entry marked failed, open it and read the error; it carries the specific reason Telegram returned for that destination.
Send /test to the bot in Telegram. That fires a sample alert through AlertSync to your destinations without involving TradingView at all. If the test arrives but your real alerts do not, the problem is on the TradingView side — usually the URL, the alert action, or your TradingView plan.
No. The Free plan delivers real webhooks — 1 webhook and 50 alerts a month. Paid plans starting at ₹149/mo add more webhooks, more alerts and multi-destination fan-out, but delivery itself is not gated. TradingView, separately, does require a paid plan for the webhook feature on their side.
Start on the Free plan — no card required — and watch your next TradingView signal land in Telegram in real-time.