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 →
{
"id": "steinheim-w05-morning-brief",
"name": "W05 \u2014 Morning brief",
"nodes": [
{
"parameters": {
"rule": {
"interval": [
{
"field": "cronExpression",
"expression": "30 9 * * *"
}
]
}
},
"id": "w05-cron",
"name": "09:30 Cairo",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
-220,
0
],
"notes": "Half an hour after the daily generation, so the brief reports on a run that has finished rather than one still in flight."
},
{
"parameters": {
"method": "POST",
"url": "__APP_URL__/api/public/automation/analytics",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "x-automation-timestamp",
"value": "={{ Date.now() }}"
},
{
"name": "x-automation-nonce",
"value": "={{ $execution.id }}-brief-{{ Date.now() }}"
}
]
},
"options": {
"timeout": 60000,
"response": {
"response": {
"neverError": true,
"fullResponse": true
}
}
}
},
"id": "w05-analytics",
"name": "Read analytics",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
20,
0
],
"credentials": {
"httpHeaderAuth": {
"name": "<your credential>"
}
}
},
{
"parameters": {
"chatId": "__TELEGRAM_CHAT_ID__",
"text": "=\u2600\ufe0f <b>Good morning</b>\n\n{{ $json.statusCode === 200 ? 'Last 7 days: ' + JSON.stringify($json.body).slice(0, 400) : 'Analytics unavailable (HTTP ' + $json.statusCode + ')' }}\n\nSend /pending to approve today's posts, or /jobs to see what ran overnight.",
"additionalFields": {
"parse_mode": "HTML"
}
},
"id": "w05-brief",
"name": "Send the brief",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1.2,
"position": [
280,
0
],
"notes": "Sent whether or not analytics answered. A morning with no message is indistinguishable from a morning where everything broke, which is the failure this brief exists to prevent.",
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
}
}
],
"connections": {
"09:30 Cairo": {
"main": [
[
{
"node": "Read analytics",
"type": "main",
"index": 0
}
]
]
},
"Read analytics": {
"main": [
[
{
"node": "Send the brief",
"type": "main",
"index": 0
}
]
]
}
},
"settings": {
"executionOrder": "v1",
"timezone": "Africa/Cairo"
}
}
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.
httpHeaderAuthtelegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
W05 — Morning brief. Uses httpRequest, telegram. Scheduled trigger; 3 nodes.
Source: https://github.com/EslaM-X/steinheim-ai-launchpad/blob/main/infra/n8n/workflows/W05-morning-brief.json — 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.
MAIA - Health Check. Uses noOp, telegram, scheduleTrigger, googleSheets. Scheduled trigger; 7 nodes.
MAIA - Health Check. Uses telegram, googleSheets, httpRequest. Scheduled trigger; 7 nodes.
9AM IST AI Daily Digest (Arxiv + GitHub + News). Uses httpRequest, llm, telegram. Scheduled trigger; 6 nodes.
Yard Stats: Daily Report. Uses httpRequest, emailSend, telegram. Scheduled trigger; 5 nodes.
W01 — Daily content generation. Uses httpRequest, telegram. Scheduled trigger; 5 nodes.