Retrieve deadlock game match statistics and send to Telegram
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs on Telegram events. Along the way it connects Telegram. It also calls deadlocktracker.gg over HTTP.
How it runs
Trigger: On Telegram events.
- Fetch Profile HTML (HTTP Request): calls deadlocktracker.gg
- Extract Match ID (Function): runs custom JavaScript (legacy Function node)
- Fetch Match HTML (HTTP Request): calls an HTTP API
- Parse Players (Function): runs custom JavaScript (legacy Function node)
- Format Message (Function): runs custom JavaScript (legacy Function node)
- Send Telegram Message (Telegram): uses Telegram
Services it uses
HTTP calls to: deadlocktracker.gg
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Extract Match ID, Parse Players, Format Message: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Extract Match ID, Parse Players, Format Message | Code node, mode 'Run Once for All Items' |
Nodes used (4)
- Telegram
n8n-nodes-base.telegram - HTTP Request
n8n-nodes-base.httpRequest - Function
n8n-nodes-base.function - Telegram Trigger
n8n-nodes-base.telegramTrigger
From the author
Deadlock Match Stats Bot is an automated workflow for n8n designed to send detailed player statistics from the most recent Deadlock match directly to Telegram. When the user sends the /match command to the Telegram bot, the workflow performs the following…