You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m trying to build a maintenance workflow with NanoBot on Telegram, and I’d like to ask for the best architectural approach.
What I want to achieve
I have a Telegram maintenance group with:
• me as the owner/admin
• engineers (for example Mohammed and Richard)
• possibly other participants
What I want is:
NanoBot should listen to all messages in the group
so it can observe the conversation
detect status updates from engineers
notice when somebody says a job is done, in progress, or blocked
But NanoBot should only treat my messages as actual commands/instructions
I want the bot to respond to me
I do not want it to start chatting with everyone in the group
ideally, other users’ messages should be treated as signals/events, not as prompts requiring a conversational reply
Optional behavior
if an engineer says something like:
“done”
“fixed”
“lamp repaired”
“still working on it”
“blocked, no spare parts”
the bot should be able to:
update task status
optionally confirm completion
or silently update a pinned task list
Reminder logic
if a task stays open too long, the bot should remind the assigned engineer politely
The problem I found
From what I understand, Telegram currently has:
• groupPolicy: "mention" or "open"
• allowFrom
But allowFrom seems to work at sender level, not as:
• “read everyone”
• “only obey admin”
• “treat engineers as status-only users”
So if I keep allowFrom restricted to myself, the bot may not process engineers’ messages at all.
If I open it up to engineers too, then I worry the bot may start treating their messages as normal prompts instead of just maintenance status updates.
My ideal behavior
I’m looking for something like this:
• Read all group messages
• Respond conversationally only to admin/owner
• Use engineers’ messages only for workflow/task state
• Ignore everyone else silently
• Optionally maintain a pinned maintenance task list in the group
In other words:
• admin → can create/manage tasks
• engineer → can update status / mark done
• others → ignored silently
My question
What is the cleanest way to implement this in NanoBot?
Would you recommend:
extending Telegram channel behavior,
using groupPolicy = open plus custom filtering,
adding role-aware logic in a skill,
or introducing a new concept like:
read permissions
command permissions
silent observers / status-only users
Bonus question
Would it make sense to support a workflow like this natively?
Example:
• bot listens to all messages in one Telegram group
• owner assigns tasks
• engineers report progress in natural language
• bot updates a pinned message with open tasks
• bot sends reminders after 24h if needed
I’d really appreciate any advice on the best pattern here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’m trying to build a maintenance workflow with NanoBot on Telegram, and I’d like to ask for the best architectural approach.
What I want to achieve
I have a Telegram maintenance group with:
• me as the owner/admin
• engineers (for example Mohammed and Richard)
• possibly other participants
What I want is:
NanoBot should listen to all messages in the group
But NanoBot should only treat my messages as actual commands/instructions
Optional behavior
Reminder logic
The problem I found
From what I understand, Telegram currently has:
• groupPolicy: "mention" or "open"
• allowFrom
But allowFrom seems to work at sender level, not as:
• “read everyone”
• “only obey admin”
• “treat engineers as status-only users”
So if I keep allowFrom restricted to myself, the bot may not process engineers’ messages at all.
If I open it up to engineers too, then I worry the bot may start treating their messages as normal prompts instead of just maintenance status updates.
My ideal behavior
I’m looking for something like this:
• Read all group messages
• Respond conversationally only to admin/owner
• Use engineers’ messages only for workflow/task state
• Ignore everyone else silently
• Optionally maintain a pinned maintenance task list in the group
In other words:
• admin → can create/manage tasks
• engineer → can update status / mark done
• others → ignored silently
My question
What is the cleanest way to implement this in NanoBot?
Would you recommend:
Bonus question
Would it make sense to support a workflow like this natively?
Example:
• bot listens to all messages in one Telegram group
• owner assigns tasks
• engineers report progress in natural language
• bot updates a pinned message with open tasks
• bot sends reminders after 24h if needed
I’d really appreciate any advice on the best pattern here.
Thanks in advance.
BaGRoS
Beta Was this translation helpful? Give feedback.
All reactions