Who this is for: anyone tracking more than one SPL token who doesn't want to run a separate workflow — and a separate Telegram bot chat — per token.
The base price alert workflow watches one mint against one threshold. This variant queries Jupiter's price API with a comma-separated list of mint addresses in a single call, checks each token's price against its own threshold, and sends one Telegram message per token that just crossed — so a five-token watchlist still costs one HTTP request every 5 minutes, not five.
TOKEN_MINT env var with a WATCHLIST env var holding a JSON array, e.g. [{"mint":"...","soglia":1.5,"direzione":"sopra"},{"mint":"...","soglia":0.02,"direzione":"sotto"}].https://price.jup.ag/v6/price?ids= followed by the mints joined with commas — Jupiter returns all requested prices in one response body.$getWorkflowStaticData.Jupiter's /v6/price endpoint accepts multiple comma-separated ids and returns a price map keyed by mint in one response, so batching tokens doesn't multiply the number of RPC/API calls — only the size of the Code node's loop grows.