Confirm the Telegram bot used in your Botsonic workflow
Get a periodic identity check for the Telegram bot your team relies on for Botsonic-related communication.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Bot Info
Get basic information about the bot using the bot api getme method.
Why this helps
When multiple bots exist, it is easy to lose track of which identity a workflow uses.
- Retrieve basic information about the Telegram bot.
- Make the bot identity visible in recurring reports.
- Reduce uncertainty when maintaining multiple bots.
Setup
Build it in a few focused steps.
- 1Connect Botsonic and Telegram to Notis once.
- 2Create a recurring automation for the bot identity check.
- 3In one instruction, ask Notis to retrieve basic information about the connected Telegram bot and report its returned identity for the team's Botsonic workflow records.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test once and confirm the returned bot is the one your team expects.
Questions about this workflow
Does the identity check verify Botsonic connectivity?
No. The listed action retrieves basic Telegram bot information. It does not verify a Botsonic connection.
Can I check several Telegram bots at once?
The listed action gets information about the connected bot. Do not assume it can inspect other bots unless they are separately connected and available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botsonic to Telegram. A trigger fires from one place; an action lands in another.
Botsonic triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Botsonic and Telegram, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Telegram.