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 →

Download .json

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.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

Play Store Publish Approval. Uses telegram, telegramTrigger, httpRequest. Webhook trigger; 9 nodes.

Source: https://github.com/IITA-AKILIMO/akilimo-mobile/blob/05c33ea72cde4f3f2809d00e3d724a5186bbb255/.n8n/playstore-approval.json — original creator credit. Request a take-down →

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

WF_UNIFIED_LEGAL_AUTOMATION. Uses googleSheets, httpRequest, telegram, telegramTrigger. Webhook trigger; 53 nodes.

Google Sheets, HTTP Request, Telegram +1

Slack & Telegram

AIPA - BMF Work Logging. Uses telegram, telegramTrigger, supabase, httpRequest. Webhook trigger; 19 nodes.

Telegram, Telegram Trigger, Supabase +1

Slack & Telegram

N8N-Approval-Workflow. Uses telegram, telegramTrigger, httpRequest, dataTable. Webhook trigger; 18 nodes.

Telegram, Telegram Trigger, HTTP Request +1

Slack & Telegram

Play Store Publish Approval. Uses telegram, telegramTrigger, httpRequest. Webhook trigger; 9 nodes.

Telegram, Telegram Trigger, HTTP Request

Slack & Telegram

N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.

Telegram Trigger, Data Table, Telegram +3