Start with one-time or recurring schedules
Owenrgram supports messages that run once as well as schedules repeated by minute, hour, day, week, or month. A task keeps its account, target conversation, content, and schedule together so the sending identity remains explicit at execution time.
Schedules live in the server-side task flow and do not require the user to keep a browser tab open. Operators can inspect, update, or disable a plan while the workspace continues to show its current state.
- One-time scheduled messages
- Minute, hour, day, week, and month recurrence
- Server-side execution without an open browser
Subscribe to group, channel, user, or keyword messages
Message subscriptions react to newly received messages. A rule can contain any of three conditions: a group or channel name, a sender username, or a keyword in the message text. This lets an operator watch one conversation source, one specific user, or one class of content.
At least one condition is required. When a rule contains several conditions, every condition must match before the action runs. For example, a rule can watch an entire channel, or narrow the subscription to messages in that channel that also contain a selected keyword.
- Match a group or channel name
- Match a sender username or message keyword
- Combine multiple conditions with AND matching
Reply to the original message or forward it
After a message matches, the automation can reply to that original message with predefined text or forward the original message to a conversation selected in the current account. Both actions keep the source account and message context explicit.
A fixed reply action does not call an AI model. Context-aware AI auto reply is a separate capability that remains limited to private chats, so a group or channel subscription does not expand the scope in which AI is allowed to respond.
- Reply to the original message with fixed text
- Forward the original message to a selected conversation
- Keep fixed automation separate from private-chat AI replies
Confirm the final result after automation runs
Schedules, message-subscription actions, and bulk jobs may all execute asynchronously. Acceptance only means the work entered the processing flow; Owenrgram continues following the Operation until it succeeds, fails, is cancelled, or expires.
When a reply or forward lacks permission or encounters Slow Mode, Flood Wait, or a network failure, the workspace preserves the real reason and Log ID. Automation does not hide Telegram permissions or rate limits, and an accepted request is not presented as completed work.
- Final Operation state determines the result
- Failure reason and Log ID remain visible
- Telegram permission and rate limits stay visible
Frequently asked questions
Must I keep the browser open for a scheduled Telegram message?
No. The server-side task flow executes the schedule; the browser configures it and displays outcomes.
Which Telegram messages can an automation subscribe to?
A rule can match a group or channel name, a sender username, or a message keyword. At least one condition is required.
What can happen after a message matches?
The automation can reply to the original message with fixed text or forward it to a conversation selected in the current account.
How do multiple subscription conditions work?
Multiple conditions in one rule use AND matching, so every configured condition must match before the action runs.