This workflow follows the HTTP Request → Telegram recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"name": "Monitorar Sites - Telegram",
"nodes": [
{
"id": "1",
"name": "Schedule Trigger",
"type": "n8n-nodes-base.cron",
"typeVersion": 1,
"position": [
250,
300
],
"parameters": {
"triggerTimes": [
{
"mode": "every5Minutes"
}
]
}
},
{
"id": "2",
"name": "Sites",
"type": "n8n-nodes-base.function",
"typeVersion": 1,
"position": [
450,
300
],
"parameters": {
"functionCode": "return [\n { json: { url: 'https://site1.com' } },\n { json: { url: 'https://2.com' } },\n { json: { url: 'https://3.com' } }\n];"
}
},
{
"id": "3",
"name": "Verificar Site",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 1,
"position": [
650,
300
],
"parameters": {
"url": "={{$json[\"url\"]}}",
"method": "GET",
"responseFormat": "string",
"timeout": 5000
}
},
{
"id": "4",
"name": "Est\u00e1 Online?",
"type": "n8n-nodes-base.if",
"typeVersion": 1,
"position": [
850,
300
],
"parameters": {
"conditions": {
"number": [
{
"value1": "={{$json[\"statusCode\"]}}",
"operation": "larger",
"value2": 199
},
{
"value1": "={{$json[\"statusCode\"]}}",
"operation": "smaller",
"value2": 400
}
]
}
}
},
{
"id": "5",
"name": "Enviar Telegram - ONLINE",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1,
"position": [
1050,
200
],
"parameters": {
"resource": "message",
"operation": "sendMessage",
"text": "O site {{$json[\"url\"]}} est\u00e1 ONLINE.",
"chatId": "-4765514962"
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
}
},
{
"id": "6",
"name": "Enviar Telegram - OFFLINE",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1,
"position": [
1050,
400
],
"parameters": {
"resource": "message",
"operation": "sendMessage",
"text": "O site {{$json[\"url\"]}} est\u00e1 OFFLINE.",
"chatId": "-4765514962"
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
}
}
],
"connections": {
"Schedule Trigger": {
"main": [
[
{
"node": "Sites",
"type": "main",
"index": 0
}
]
]
},
"Sites": {
"main": [
[
{
"node": "Verificar Site",
"type": "main",
"index": 0
}
]
]
},
"Verificar Site": {
"main": [
[
{
"node": "Est\u00e1 Online?",
"type": "main",
"index": 0
}
]
]
},
"Est\u00e1 Online?": {
"main": [
[
{
"node": "Enviar Telegram - ONLINE",
"type": "main",
"index": 0
}
],
[
{
"node": "Enviar Telegram - OFFLINE",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {},
"tags": []
}
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
telegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Monitorar Sites - Telegram. Uses httpRequest, telegram. Scheduled trigger; 6 nodes.
Source: https://gist.github.com/thiagozalinsky/384c7ad961e0ba458b29c3a32359033d — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Auto Hunt. Uses httpRequest, googleSheets, rssFeedRead, telegram. Scheduled trigger; 78 nodes.
Auto-Hunt. Uses httpRequest, googleSheets, rssFeedRead, telegram. Scheduled trigger; 78 nodes.
This workflow runs daily at 9 AM, uses Perplexity to compile vaping industry news, optionally captures article screenshots via Browserless, and generates a HeyGen avatar video from a template. It then
. Uses googleSheets, telegram, httpRequest, wise. Scheduled trigger; 36 nodes.
GNCA AI News Pipeline. Uses rssFeedRead, httpRequest, telegram, errorTrigger. Scheduled trigger; 31 nodes.