Automated Telegram UserBot session monitoring & recovery with TelePilot
UnknownWhat this workflow does
This AI workflow has 13 nodes and runs on a schedule (every day at 08:00) (plus 1 other trigger). Along the way it connects Telegram and Telepilot (community).
How it runs
Trigger: On a schedule (every day at 08:00) (plus 1 other trigger).
- Get Session Status (Edit Fields (Set)): sets 3 fields: sessionId, action, chatInput
- Manual control (Tele Pilot): work with login
- Automatic control (Tele Pilot): work with login
- Pass on Closed Status (Filter): keeps only the items that match a condition
- Send Closed Status message (Telegram): uses Telegram
- Stop Session (Edit Fields (Set)): sets 3 fields: sessionId, action, chatInput
- Stop auth (Tele Pilot): work with login
- Start Session (Edit Fields (Set)): sets 3 fields: sessionId, action, chatInput
- Start auth (Tele Pilot): work with login
- Check Session Connection (Filter): keeps only the items that match a condition
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @telepilotco/n8n-nodes-telepilot is verified or supports 3.0 (used in Stop auth, Start auth, Manual control).
Nodes used (6)
- Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Tele Pilot
@telepilotco/n8n-nodes-telepilot.telePilot - Edit Fields (Set)
n8n-nodes-base.set - Filter
n8n-nodes-base.filter - Telegram
n8n-nodes-base.telegram
From the author
Disclaimer: This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Important distinction: This template manages Telegram Copilot's UserBots (client accounts), not Telegram Bots. UserBot vs. Bot: Key Differences 🔹…