My automated sports-betting workflow in n8n is misbehaving: the N8N workflow API is handing back incorrect data, which then gets pushed straight into my Discord channel. Because of that every new game line shows the wrong odds and settles the wrong way. I need the root cause isolated and fixed today so the feed is reliable again. Here is the current setup in broad strokes. The workflow pulls game lines from a sports data API, processes them through several n8n nodes, and finally posts updates to Discord. Somewhere between retrieval and output the figures are being distorted, but I have not pinned down the exact node—so you’ll need to trace the whole chain. What I expect from you today • Audit the existing n8n nodes, credentials and expressions to locate where the data shifts from correct to incorrect. • Patch or rebuild the offending section so the numbers match the raw sports data API response. • Test end-to-end—trigger, transform, and Discord post—until live odds and results display accurately. • Give me a quick rundown of what was wrong and how you fixed it, so I can maintain the flow later. You’ll be working directly in n8n (self-hosted) and Discord webhooks; no other services are involved. Speed matters, so please be ready to jump in right away and deliver a clean, working automation before the day is out.