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": "Telegram About Me Bridge",
"nodes": [
{
"parameters": {
"updates": [
"message"
],
"additionalFields": {}
},
"id": "Telegram_Trigger",
"name": "Telegram Trigger",
"type": "n8n-nodes-base.telegramTrigger",
"typeVersion": 1.1,
"position": [
220,
280
]
},
{
"parameters": {
"jsCode": "const message = $json.message?.text || '';\nconst chatId = $json.message?.chat?.id;\nreturn [{ json: { message, chatId } }];"
},
"id": "Code_Prepare",
"name": "Code Prepare",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
450,
280
]
},
{
"parameters": {
"method": "POST",
"url": "https://api.pklavc.com/chat",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "Content-Type",
"value": "application/json"
},
{
"name": "Authorization",
"value": "Bearer {{$env.CHATBOT_API_TOKEN}}"
}
]
},
"sendBody": true,
"specifyBody": "json",
"jsonBody": "={\n \"message\": \"{{$json.message}}\",\n \"conversation_id\": \"telegram-{{$json.chatId}}\"\n}",
"options": {}
},
"id": "HTTP_Chat_API",
"name": "HTTP Chat API",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
690,
280
]
},
{
"parameters": {
"chatId": "={{$node['Code Prepare'].json['chatId']}}",
"text": "={{$json.reply}}",
"additionalFields": {}
},
"id": "Telegram_Send",
"name": "Telegram Send Message",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1.2,
"position": [
940,
280
]
}
],
"connections": {
"Telegram Trigger": {
"main": [
[
{
"node": "Code Prepare",
"type": "main",
"index": 0
}
]
]
},
"Code Prepare": {
"main": [
[
{
"node": "HTTP Chat API",
"type": "main",
"index": 0
}
]
]
},
"HTTP Chat API": {
"main": [
[
{
"node": "Telegram Send Message",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1"
}
}
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Telegram About Me Bridge. Uses telegramTrigger, httpRequest, telegram. Event-driven trigger; 4 nodes.
Source: https://github.com/PkLavc/PkLavc.github.io/blob/main/src/chatbot/workflows/telegram-about-me-template.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.
N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.
Pede Ai. Uses httpRequest, telegram, postgres, telegramTrigger. Event-driven trigger; 57 nodes.
TextMain. Uses telegramTrigger, stopAndError, telegram, httpRequest. Event-driven trigger; 56 nodes.
Pede Ai. Uses httpRequest, telegram, postgres, telegramTrigger. Event-driven trigger; 53 nodes.
📄 Documentation: Notion Guide