Telegram Batch Messaging: Timezone-Safe Automation
Distributed teams get spammed by notifications across timezones. Notis batches your updates and posts them once per region at a sensible local time.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Message
Send a text message to a telegram chat using the bot api.
Why this helps
With team members in 5 timezones, sending notifications throughout the day means someone is always getting pinged at 3 AM. Batching helps, but manual scheduling is tedious. Notis automates timezone-aware batching.
- Team members aren't pinged at odd hours
- Reduce notification spam and chat fatigue
- Respect different work schedules
- Neurodivergent workers appreciate predictable update times
Setup
Build it in a few focused steps.
- 1Connect Telegram to Notis and tell Notis your team's primary timezones.
- 2Ask Notis: 'Batch all our daily updates and post them to Telegram at 9 AM in each person's local timezone.'
- 3Set the trigger to 'Recurring Schedule' and specify the time and frequency (e.g., daily at 9 AM).
- 4Notis collects updates throughout the day and sends one consolidated message per timezone.
- 5Test: watch a few days of batched messages and adjust the time if it doesn't feel right for your team.
Questions about this workflow
How do I tell Notis to batch only certain updates?
Tell Notis which channels or keywords to include (e.g., 'batch only announcements, not urgent alerts'). Urgent items can still go out immediately; the batching applies to routine updates.
Can I have different batch times for different teams?
Yes. Create separate automations for engineering, marketing, etc., each with its own schedule and timezone rules.
What if someone needs an update before the batch goes out?
Notis can send urgent alerts separately (outside the batch). Tell Notis which keywords or tags mean 'send immediately,' so routine updates batch but critical ones go out right away.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Telegram. A trigger fires from one place; an action lands in another.
Fireflies triggers
Telegram actions
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just Fireflies and Telegram. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.