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": "PROD_01_API_Integration_Workflow",
"nodes": [
{
"parameters": {
"httpMethod": "GET",
"path": "api-integration",
"responseMode": "lastNode",
"options": {}
},
"id": "1",
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"typeVersion": 1,
"position": [
250,
300
]
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "1",
"name": "endpoint",
"value": "{{ $json.body.endpoint }}",
"type": "string"
},
{
"id": "2",
"name": "method",
"value": "{{ $json.body.method }}",
"type": "string"
},
{
"id": "3",
"name": "payload",
"value": "={{ $json.body.payload }}",
"type": "object"
}
]
}
},
"id": "2",
"name": "Parse_Request",
"type": "n8n-nodes-base.set",
"typeVersion": 3,
"position": [
450,
300
]
},
{
"parameters": {
"method": "{{ $json.method }}",
"url": "{{ $json.endpoint }}",
"sendBody": true,
"bodyParameters": {
"parameters": [
{
"name": "data",
"value": "={{ JSON.stringify($json.payload) }}"
}
]
},
"options": {}
},
"id": "3",
"name": "HTTP_Request",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4,
"position": [
650,
300
]
},
{
"parameters": {
"jsCode": "const response = $input.first().json;\nconst result = {\n success: response.status >= 200 && response.status < 300,\n status_code: response.status,\n data: response.data || response,\n processed_at: new Date().toISOString()\n};\nreturn result;"
},
"id": "4",
"name": "Format_Response",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
850,
300
]
},
{
"parameters": {
"to": "api_monitoring",
"text": "={{ 'API Call: ' + $json.endpoint + ' | Status: ' + $json.status_code + ' | Success: ' + $json.success }}",
"additionalFields": {}
},
"id": "5",
"name": "Telegram_Log",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1,
"position": [
1050,
300
]
}
],
"connections": {
"Webhook": {
"main": [
[
{
"node": "Parse_Request",
"type": "main",
"index": 0
}
]
]
},
"Parse_Request": {
"main": [
[
{
"node": "HTTP_Request",
"type": "main",
"index": 0
}
]
]
},
"HTTP_Request": {
"main": [
[
{
"node": "Format_Response",
"type": "main",
"index": 0
}
]
]
},
"Format_Response": {
"main": [
[
{
"node": "Telegram_Log",
"type": "main",
"index": 0
}
]
]
}
},
"settings": {
"executionOrder": "v1"
},
"versionId": "prod-01-v1",
"id": "PROD01APIINTEGRATION",
"tags": [
{
"name": "production"
},
{
"name": "integration"
}
]
}
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
PROD_01_API_Integration_Workflow. Uses httpRequest, telegram. Webhook trigger; 5 nodes.
Source: https://gist.github.com/duginsash-spec/c0128580e71defd5f25f609991be219a — 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.
WF_UNIFIED_LEGAL_AUTOMATION. Uses googleSheets, httpRequest, telegram, telegramTrigger. Webhook trigger; 53 nodes.
qualiopi. Uses airtable, telegram, emailSend, httpRequest. Webhook trigger; 51 nodes.
PsyCardv2. Uses executeCommand, telegram, readBinaryFile, googleDrive. Webhook trigger; 41 nodes.
[](https://www.linkedin.com/in/mosaab-yassir-lafrimi/)[](https://t.me/joevenner)
How it works • Webhook triggers from content creation system in Airtable • Downloads media (images/videos) from Airtable URLs • Uploads media to Postiz cloud storage • Schedules or publishes content a